💾 Archived View for gemi.dev › gemini-mailing-list › 000955.gmi captured on 2023-11-04 at 13:13:39. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
=> https://singletona082.flounder.online/ HTTP flavor => gemini://singletona082.flounder.online/ Gemini flavor the web proxy renders it as raw gemtext, and lagrange says 'preformatted text without caption' until I click on it and then it behaves 'correctly' Then again the server itself seems to have gone down. So that may be relevant. I'm just 'what did I do wrong'? The fact this happens right as I swap back to linux and thus FTP clients feels not coincidental.
On Sun, Jul 04, 2021 at 04:28:38PM -0500, Andrew Singleton <singletona082 at gmail.com> wrote a message of 32 lines which said: > the web proxy renders it as raw gemtext, and lagrange says 'preformatted > text without caption' until I click on it and then it behaves 'correctly' Strange, since I see no preformatted text on this page. > Then again the server itself seems to have gone down. Works for me.
Removed the predormstted text to see if that was the issue. On both. Main index and gemlog index first lines aren't rendering (shows the h1#) unsure why it would do that past the fact for some danged reason filesilla opened the gmi files in ligroffice (by default it opens in xed if I just double click on the file.) Jul 5, 2021 2:28:07 AM Stephane Bortzmeyer <stephane at sources.org>: > On Sun, Jul 04, 2021 at 04:28:38PM -0500, > Andrew Singleton <singletona082 at gmail.com> wrote > a message of 32 lines which said: > >> the web proxy renders it as raw gemtext, and lagrange says 'preformatted >> text without caption' until I click on it and then it behaves 'correctly' > > Strange, since I see no preformatted text on this page. > >> Then again the server itself seems to have gone down. > > Works for me.
On Mon Jul 5, 2021 at 2:33 PM BST, Andrew Singleton wrote: > Removed the predormstted text to see if that was the issue. On both. > Main index and gemlog index first lines aren't rendering (shows the h1#) > unsure why it would do that past the fact for some danged reason > filesilla opened the gmi files in ligroffice (by default it opens in xed > if I just double click on the file.) i might be picking up the wrong end of the stick here but: would a space after the # help fix things and the page source has a <feff> in front of the # when page sourced from Lagrange and fed direct to vim or via mousepad and then vim : ?#Cheapie Theatre my own page source again from lagrange starts with just a #: # neil in gemini space could be a non-printing nasty char in the file. Cheers Neil
Nice thought but sadly no. May just rcrat and reupload the file to see if libre office did some kind of funky thing. Jul 5, 2021 9:26:54 AM neil c timms <mingmengtou at use.startmail.com>: > On Mon Jul 5, 2021 at 2:33 PM BST, Andrew Singleton wrote: >> Removed the predormstted text to see if that was the issue. On both. >> Main index and gemlog index first lines aren't rendering (shows the h1#) >> unsure why it would do that past the fact for some danged reason >> filesilla opened the gmi files in ligroffice (by default it opens in xed >> if I just double click on the file.) > i might be picking up the wrong end of the stick here but: > > would a space after the # help fix things and the page > source has a <feff> in front of the # when page sourced > from Lagrange and fed direct to vim or via mousepad and then vim > : > ?#Cheapie Theatre > > my own page source again from lagrange starts with just a #: > # neil in gemini space > > could be a non-printing nasty char in the file. > Cheers Neil
On Mon Jul 5, 2021 at 5:20 PM BST, Andrew Singleton wrote: > Nice thought but sadly no. May just rcrat and reupload the file to see > if libre office did some kind of funky thing. > > > source has a <feff> in front of the # when page sourced > > from Lagrange and fed direct to vim or via mousepad and then vim it still looks like your source page starts with <efff> a bom (byte order mark). " Its presence interferes with the use of UTF-8 by software that does not expect non-ASCII bytes at the start of a file but that could otherwise handle the text stream." (https://en.wikipedia.org/wiki/Byte_order_mark) i had included it in my scrape of your page from Lagrange but i guess that it was filtered out for good reason in the trip from here to there, etc. i suggest looking at your page source from Lagrange in an editor that supports making the invisible visible:-) Other pages i scraped do not start with a bom. I now remember having a battle with a bom many moons ago: most confusing things as we can't see them easily yet they cause us pain. Live long and prosper V Neil
Dude, thanks. So ya. Next step is figuring out how to make filesilla use an actual text editor instead of opening freaking office. Appreciate the help. Jul 5, 2021 1:48:18 PM neil c timms <mingmengtou at use.startmail.com>: > On Mon Jul 5, 2021 at 5:20 PM BST, Andrew Singleton wrote: >> Nice thought but sadly no. May just rcrat and reupload the file to see >> if libre office did some kind of funky thing. >> >>> source has a <feff> in front of the # when page sourced >>> from Lagrange and fed direct to vim or via mousepad and then vim > it still looks like your source page starts with <efff> a bom > (byte order mark). " Its presence interferes with the use of UTF-8 by > software that does not expect non-ASCII bytes at the start of a file but > that could otherwise handle the text stream." > (https://en.wikipedia.org/wiki/Byte_order_mark) i had included it in my > scrape of your page from Lagrange but i guess that it was filtered out > for good reason in the trip from here to there, etc. i suggest looking > at your page source from Lagrange in an editor that supports making the > invisible visible:-) Other pages i scraped do not start with a bom. > I now remember having a battle with a bom many moons ago: most > confusing things as we can't see them easily yet they cause us pain. > Live long and prosper V Neil
Alright ya, using notepad++ to specifically remove BaoM fixed the problem. Again appcist the help, and credited the list on the blog post announcing the fix. Jul 5, 2021 4:16:48 PM Andrew Singleton <singletona082 at gmail.com>: > Dude, thanks. > > So ya. Next step is figuring out how to make filesilla use an actual text editor instead of opening freaking office. > > Appreciate the help. > > Jul 5, 2021 1:48:18 PM neil c timms <mingmengtou at use.startmail.com>: > >> On Mon Jul 5, 2021 at 5:20 PM BST, Andrew Singleton wrote: >>> Nice thought but sadly no. May just rcrat and reupload the file to see >>> if libre office did some kind of funky thing. >>> >>>> source has a <feff> in front of the # when page sourced >>>> from Lagrange and fed direct to vim or via mousepad and then vim >> it still looks like your source page starts with <efff> a bom >> (byte order mark). " Its presence interferes with the use of UTF-8 by >> software that does not expect non-ASCII bytes at the start of a file but >> that could otherwise handle the text stream." >> (https://en.wikipedia.org/wiki/Byte_order_mark) i had included it in my >> scrape of your page from Lagrange but i guess that it was filtered out >> for good reason in the trip from here to there, etc. i suggest looking >> at your page source from Lagrange in an editor that supports making the >> invisible visible:-) Other pages i scraped do not start with a bom. >> I now remember having a battle with a bom many moons ago: most >> confusing things as we can't see them easily yet they cause us pain. >> Live long and prosper V Neil
---
Previous Thread: [ANN] tanelorn.city is shut down
Next Thread: [USER] Weird Title Rendering on Various Clients