💾 Archived View for rawtext.club › ~sloum › geminilist › 006856.gmi captured on 2023-12-28 at 16:15:00. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Andrew Singleton singletona082 at gmail.com
Wed Jul 7 01:08:11 BST 2021
- - - - - - - - - - - - - - - - - - -
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