Re: "Cyrillic text in filenames? I can't find any information…"

In: s/nex

I don't recall if I ever verified whether Lagrange behaves in a sane way when it comes to Nex and URI percent-encoding... It's very possible that it doesn't work as intended (encode after receiving Nex index, decode when sending Nex request).

🌆 skyjake [sysop]

2025-09-10 · 8 months ago

1 Later Comment

👻 ps [OP] · 2025-09-10 at 13:20:

I recently checked, and it seems that Lagrange is working well. However, there is a server-side issue (Yseterweb) where I should store the filenames URL-encoded, lol.

🌒 s/nex

👻 ps:

Cyrillic text in filenames? I can't find any information about this in the specification: [nex link] When trying to URL-encode, the Lagrange browser does not decode these names in listing view. There is also no Alt text option, as implemented in Gemtext. If the Nex protocol is ASCII-oriented, it should be mentioned somewhere in the specification. /s/nex/32478 Yet another related subject

💬 2 comments · 2025-09-10 · 8 months ago