💾 Archived View for rawtext.club › ~sloum › geminilist › 001812.gmi captured on 2020-10-31 at 02:32:10. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Luke Emmet luke.emmet at gmail.com
Sat Jun 20 08:42:20 BST 2020
- - - - - - - - - - - - - - - - - - -
Hi Sean
Thanks for the new tests - I just ran them on GemiNaut.
I believe my client GemiNaut is doing the right thing for all of them. But this is because I'm using a system web browser control to do the hard work of the text rendering. Apart from the ones mentioned below which I disagree with, it wraps them all as I would expect.
The only quibble I would have with the tests is the ones with no spacers at all (43, 46 and 49). I don't agree that the client should try to hyphenate the words. Doing so is a non-trivial problem and for a real language is very language specific (where are the syllable boundaries perhaps). So the correct thing to do is to simply lay them out in a non-wrapped line. I don't think there could be any authority about how to wrap an arbitrary sequence of unicode points? If there is such a thing please say.
So I think for those tests, you should say that the client should not crash, but should display either a) as a wrapped link (wrapped any old how for those clients that insist on forcing a wrap, perhaps on mobile or b) as a single unwrapped line with a scrolling mechanism.
A suggestion for a possible improvement - it would be helpful if there was a "back to tests index" link on each page, that way you can choose a few tests from the index, then go back to the index when you are done - otherwise you might have to go back N times, which is not quite as nice.
Best Wishes
- Luke
On 20-Jun-2020 02:28, Sean Conner wrote:
I just added 10 new tests to the Gemini Client Torture Test, tests 41
through 50. They all test section 5.4.1 of the Gemini Specification (text
lines). Each page contains a line that exceeds 8,500 bytes (yes, bytes, not
characters, although some of then exceed 8,500 characters, depends upon the
characters used). A few mild spoilers:
Some have the spaces replaced with dashes.
Some have no spaces, dashes or any puntuation to speak of.
Some have Unicode combining characters.
I do apologize for the snark in test 50, but it represents one of the many
aspects that I dislike about Unicode in general.
I expect these tests to be among the hardest to deal with for a client.
You have been warned. If anyone thinks these tests are unfair, well, here's
the thread to discuss it.
-spc