kenobi
12/2/2015 4:01:00 PM
W dniu wtorek, 1 grudnia 2015 18:44:00 UTC+1 uzytkownik Mark Carroll napisal:
> On 01 Dec 2015, fir wrote:
>
> > Im personally still using asci in all my private apps and i shiver (a bit) to
> > use unicode as i read from time to time text that says unicode is a pain (at
> > least in some situations)
>
> Yes. There is a lot of complexity mixed in with it, rather entailed by
> the problems it aims to solve.
>
> > This directs me to think that unicode is in general a fail.. Unicode could go
> > the way and become something maybe even simpler than ascii but gone a bit in a
> > wrong way of making a lot additional mess
>
> It's very widely used now though. For a lot of my workflows, via various
> languages and libraries, they're cleanly Unicode all the way through,
> requiring little work on my own part to achieve that. Waiting a while
> was key, now there is all manner of free built-in stuff and third-party
> libraries, like Pango's support for OpenType fonts, that will do much of
> the common harder stuff for you. It's really only quite rarely, with
> rather old software (like Basser Lout, which has been in maintenance
> mode for years) or old protocols (e.g., Reverse Gossip Transfer
> Protocol!) that are instead ISO-8859-based, where I find anything
> lacking these days. I rarely have to think about it all except, for
> instance, in small ways like when trying to support Python 2.7 scripts
> that still need a u-prefix for literals, or remembering to use XeTeX
> instead of LaTeX.
>
> For a while now, the main software I work on has required a Unicode
> database backend, and I don't recall any of our users complaining. (We
> handle dimensioned units like µm and Å.)
>
> > I thing then that maybe one posible recovery scenerio is to use damn utf-32
> > only, everywhere you coud and try to forget and deprecate the other part of
> > the mess
> >
> > what do ya think?
>
> Yes, at least I usually see UTF-8 or UTF-16 in use, and I try to just
> use those all the way through. Similarly, with other complications like
> time zones, I like to just use UTC / Zulu all the way through and just
> convert in the presentation layer.
>
> Personally, I'd be happy with ISO-8859-15 plus arrows, but I'm not
> having to handle text in Chinese, Arabic, etc. True l10n and i18n even
> just in Western Europe come with all manner of tricky challenges
> presented by the inconvenient complexity of the real world.
>
tnx for comment
i think general convention of using utf-32 everywhere could repair this mess maybe though 1) some maybe can see this crazy as utf-32 is probably now least used 2) im not sure (if utf-32 is as simple as it should i mean one letter is one 32-bit int in memory and no other things do occur)