It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Gede: Regarding the “funny quotes”, since they are Unicode now, software has no excuse not to play ball with them. The problem is mostly due to those guys who think that “7 bits per character ought to be enough for anybody”.
There are loads of more-or-less useful characters that GOG completely bugs out at.
Post edited April 20, 2016 by Maighstir
avatar
Gede: Regarding the “funny quotes”, since they are Unicode now, software has no excuse not to play ball with them. The problem is mostly due to those guys who think that “7 bits per character ought to be enough for anybody”.
avatar
Maighstir: There are loads of more-or-less useful characters that GOG completely bugs out at.
It does!? :-S
I have not noticed it. Do you remember some?

But that reminds me I have something to say to Wishbone:
avatar
Wishbone: I only recently learned that UTF-32 actually exists, although I cannot for the life of me figure out why anyone would need it, or why anyone would think using it for anything would be a good idea.
Here are my thoughts, though I have not done proper research on it.
If your text uses mainly code points exceeding U+FFFF, I think you will see a reduction on the overall document size if you encode it with UTF-32 rather than UTF-16 or UTF-8.
I don't think there are many texts where this size reduction is very meaningful, but there is one more difference. Contrary to the UTF-8 and UTF-16, UTF-32 is a fixed-size encoding. This means that transforming or addressing any character is a trivial matter.
avatar
Gede: If your text uses mainly code points exceeding U+FFFF, I think you will see a reduction on the overall document size if you encode it with UTF-32 rather than UTF-16 or UTF-8.
I don't think there are many texts where this size reduction is very meaningful, but there is one more difference. Contrary to the UTF-8 and UTF-16, UTF-32 is a fixed-size encoding. This means that transforming or addressing any character is a trivial matter.
While having a fixed character size certainly makes some things easier, a fixed size of 4 bytes brings in so much overhead that I really don't think it's worth it for any scenario I can imagine.
avatar
Gede: Don't even mention "Comic Sans" near them.
Comic Sans is a thing of sublime beauty compared to Arial.
avatar
Gede: If your text uses mainly code points exceeding U+FFFF, I think you will see a reduction on the overall document size if you encode it with UTF-32 rather than UTF-16 or UTF-8.
I don't think there are many texts where this size reduction is very meaningful, but there is one more difference. Contrary to the UTF-8 and UTF-16, UTF-32 is a fixed-size encoding. This means that transforming or addressing any character is a trivial matter.
avatar
Wishbone: While having a fixed character size certainly makes some things easier, a fixed size of 4 bytes brings in so much overhead that I really don't think it's worth it for any scenario I can imagine.
There are more problems with UTF-32 than simply quadrupling disk space requirement.
Computerphile explains, at least partially.
Post edited April 21, 2016 by Maighstir
avatar
Maighstir: There are more problems with UTF-32 than simply quadrupling disk space requirement.
Computerphile explains, at least partially.
That is a very nice Youtube channel. Thanks a lot for linking to it.

Well... I did miss that, yes.However, that is not something you could not overcome. Ideally you would produce your own routines to handle Unicode data, I suppose.

avatar
ydobemos: Comic Sans is a thing of sublime beauty compared to Arial.
I'm denouncing you to the font police right now! :-P
Post edited April 23, 2016 by Gede
So has anybody from GOG team commented on this issue? Solving it might not be easy, I don't know. But it is a pretty stupid problem, and hinders everybody's ability to read text, which is quite a very basic thing.
avatar
ShreddingDragon: So has anybody from GOG team commented on this issue?
Yes. Aware of it and working on it.
avatar
ShreddingDragon: So has anybody from GOG team commented on this issue?
avatar
JMich: Yes. Aware of it and working on it.
Good to hear! Thanks for the heads-up.