News for hackers. Stuff that matters.
Re:Unicode Proposal – Textile Care Symbols by dmurray on Thursday April 22, 2021 @07:15AM (#26901416)
Having different displays for different markets is exactly what Unicode allows for: you specify the intended symbol, and then it's localised in the font you choose. An example from the proposal is "flat dry when wet, European variant has two bars, US and Canadian variant has three bars".

A glyph in one font may look confusingly similar to a completely different glyph in another font (or the same font). If you don't have a digital version you then have to rely on context clues. You can quite reliably tell if a given C is LATIN CAPITAL LETTER C or CYRILLIC CAPITAL LETTER ES, by assessing the surrounding text and the medium to see if the author was most likely writing for a Russian or an English audience.

Of course, it's possible that manufacturers currently mix contexts confusingly. In that case, having each one draw from a single Unicode palette should help.

Re:Unicode Proposal – Textile Care Symbols by grishka on Thursday April 22, 2021 @07:58AM (#26901728)
This whole "is it Cyrillic or Latin" confusion sometimes does happen IRL. There's an insurance company that has its logo in all capitals: PECO. For most of my life I've always read it as Latin. But at some point I heard it in a TV commercial and they said it as "reso". Yikes.

Also РОСНАНО. It's not "pochaho", it's "rosnano".

The reverse is also true: there's a "Bona Capona" restaurant but its logo uses a typeface that makes it tempting to read it as "Vopa Saropa".

Re:Unicode Proposal – Textile Care Symbols by aasasd on Thursday April 22, 2021 @05:24PM (#26908394)
Well thankfully the rest of the world aren't subjected to the Cyrillic-Latin confusion, because it's only inside the country that Russian companies use the mix of Cyrillic and Latin... And specifically English, while a lot of people over twenty-five can't pronounce or read English.
Re:Unicode Proposal – Textile Care Symbols by grishka on Friday April 23, 2021 @01:02AM (#26911132)
I'm genuinely envious to people who can get by with just a single keyboard layout.
Re:Unicode Proposal – Textile Care Symbols by dmurray on Thursday April 22, 2021 @07:09PM (#26909230)
Anyone who needs to deal with the language formerly known as Serbo-Croat might disagree.
Re:Unicode Proposal – Textile Care Symbols by aasasd on Thursday April 22, 2021 @07:56PM (#26909552)
Ah, well, I should've written ‘Russian-Latin confusion’—forgot about the alphabet changeovers. But at least I'm told that:

> It can be written in Serbian Cyrillic or Gaj's Latin alphabet, whose thirty letters mutually map one-to-one, and the orthography is highly phonemic in all standards.

Though digraphs spoil the clarity somewhat.

Which reminded me that I should check what Kazakhstan is doing to its language. They seem to at least have avoided the eldritch monstrosity of Polish with ‘Grzegorz Brzęczyszczykiewicz’ and the like (https://www.youtube.com/watch?v=AfKZclMWS1U). But they are still setting themselves up for English-language people pretending they can pronounce anything Latin-looking—despite English itself demanding you memorize the dictionary twice, for speaking and writing. So Kazakhstan will soon have its own great writer Karel Kaypek.

Re:Unicode Proposal – Textile Care Symbols by leoedin on Thursday April 22, 2021 @07:33AM (#26901548)
Are fonts consistently localised? What happens if the pool of people who use a font (eg Arial) contain multiple washing symbol regions? Do you spin up a new, localised font for every country?
Re:Unicode Proposal – Textile Care Symbols by TheRealPomax on Thursday April 22, 2021 @12:10PM (#26904419)
No, you simply rely on your tooling, which should allow you to set the locale (or "script", which is the OpenType term for it) for your content.

Thankfully, a lot of tooling designed to present text to a human (From Word to LaTeX to HTML) already have ways to do this, so folks writing textile documentation will now be able to take advantage of this, too.