Unicode Proposal – Textile Care Symbols
github.com
github.com
https://jameshrisho.com/2020/10/making-laundry-less-terrible...
Edit: Consider also that the shorter you run the dryer for, the shorter you are running the (substantial) motor and fan, as well as less time spent heating the shell of the dryer and the air surrounding it.
Edit: 20:1 mentioned here https://qr.ae/pGNTie
Total power usage for full heat is (5000W + 250W) * 0.5h = 2625 Wh
Total power usage for half heat is (2500W + 250W) * 1h = 2750 Wh
So that's a 4.6% increase in efficiency for using full heat over half heat.So the big question remains, does lower heat dry clothes more efficiently, and if so, how much?
The Stack Overflow answer you linked raises some interesting points, but doesn't seem rigorous.
You'll notice this in heat pump dryers. They cannot generate the same amount of heat. They take way longer to dry the clothes. But they're way more energy efficient than other forms of dryers.
Edit: I thought of another example. Heating your home with hot water running through radiators. It's significantly more energy efficient to reduce the temperature of the water. This outweighs the additional time it takes to heat up your home. There are various drawbacks and considerations though, e.g. if the house has terrible insulation (noticeable draft) then it'll not be beneficial. There's various other things that'll significantly reduce energy usage, this while anyone would assume that generating heat is already very efficient.
Edit: Also it's not that using lower-temperature water to convey heat is somehow more efficient, the thing with heat pumps is that they are more efficient at heating things to a lower temperature. If you're burning gas it doesn't really matter either way, you just get the energy out you put in.
Edit: too much metal on clothing...
https://www.energy.gov/eere/articles/no-heat-no-problem-ultr...
My heat pump dryer came with an energy estimate for various functions and loads. The various functions which shorten the time, or the functions which increase the heat (often related) are specified to use way more energy. To me, it's pretty clear, plus the manufacturer specifies it.
> Also it's not that using lower-temperature water to convey heat is somehow more efficient. [..] If you're burning gas it doesn't really matter either way, you just get the energy out you put in.
That's what I used to assume as well. It isn't accurate though. If the water that comes back to the heating element is too hot it'll not be as efficient as when the temperate is lower. Similarly, the additional energy that's needed to heat the water to e.g. 75+ degrees Celsius is wasteful. You can save around 30% of the energy by reducing the temperature of the water that's used to heat your home (though might not work due to various considerations). There are loads of other things that are possible which also significantly reduce the energy usage.
Regarding how to save energy when using a boiler there's a huge Dutch topic about it with loads of tips: https://gathering.tweakers.net/forum/list_messages/2027810. I assume similar information can be found in other languages, though heating using gas and water is really popular in NL (more so than any other country I assume).
They might still be true though, but if you keep in mind that it takes about 5 times more energy to evaporate water than to heat it to 100C, and that heating water is more difficult than most other substances it is really not clear why using more heat would be (far) less efficient. Sure it would consume heat at a higher rate, but also less long.
That depends. For resistive electric it shouldn't make a difference, pretty much all heat is transported.
For non-condensing gas (or wood etc.), if your heater is going full blast and a lot of the heat goes up your chimney and lowering the temperature makes a smaller, slower flame, that gets absorbed better, I think you could get 10-30% difference. The heating of water itself to 20℃, 75℃ or 110℃ shouldn't make much of difference, as you're not supposed to cool the effluents too much, or you get condensation, acids, rust ... which will likely kill you equipment.
Condensing gas is cool, extracting so much heat, that water condenses, but the gas must be clean enough and the condenser resistant to corrosion. Here, lowering water temperature can safely lower the effluent gas temperature for more heat extraction (even in optimal power range), and condensation of resulting water vapor from burning gas is about 10% extra energy that would otherwise go up the chimney. I'd expect about 15-30% more heat than non-condensing, especially if run on lower temperatures.
Heat pumps are quite efficient at moving heat, where 1W of electricity can move 3W of heat for a 4W heating yield. A steeper gradient means more work, so pumping heat from 20℃ to 75℃, 1W may only move 0.5W of heat for 1.5W yield (numbers not accurate). Lowering the temperature can make a 2x difference, or even more in extreme cases.
Right, it doesn't have to, but it's also possible that more heat makes it take proportionally less time (or close enough, with negligible decrease in efficiency).
Obviously, yes, using a heat pump will use less energy than a resistive heating element. But the question is more about how much and how quickly heat is input (regardless of how it was generated) and how that affects drying times.
Some places you pay for the joules delivered into your home. You have flow meter and temperature meters on he input and the output of the radiators and the price for joule is constant regardless of input and output temperatures.
What saves you money is keeping your interior cooler because heat loss is propotional to the temaperature difference.
Unfortunately I only have a Dutch link which goes into way more detail: https://gathering.tweakers.net/forum/list_messages/2027810.
Dutch energy companies by law have to advise their customers how to save money. The app I use give exactly this advice (lower the temperature), plus various other advices.
> Some places you pay for the joules delivered into your home
That's something different than what I said, no? I'm talking about when you generate the heat in your home. I'm aware of that solution as well, they're efficient because of volume plus part of the heat (energy required) is waste-heat from some industry.
There's still various ways to save energy despite exactly measuring the temperature out and in. E.g. radiator fans.
I know this all seems entirely illogical. Energy in (or required) should stay the same. Practically though, it's probably energy losses that somehow occur and are avoided.
E.g. for the radiator fans people measured if they save energy. They do, though the cost of buying them might outweigh the savings. DIY is cheap though.
Someone is paying to heat that water, and that someone would get a bit more efficiency out of the system if the water temperatures were lower.
If you generate energy inside your isolated house and transfer it to radiators also inside your house temperature shouldn't matter.
Until near the end of the cycle your dryer is putting all the energy into evaporating water, so the temperature inside the dryer is actually fairly cool. Right at the end things change as the remaining water isn't enough to counteract all the energy being put in and so you heat the clothing to no purpose. So at the end off the cycle you should either shut off with a little moisture in the clothing, or regulate the temperature so that the heat input is balanced by the water evaporation.
What on earth is thermostat heater, you ask? Surprisingly, many dryers apparently have a simple fixed-temperature thermostat, and in order to make lower settings work, a heating element tricks that thermostat into perceiving a higher temperature.
If that heating element doesn't do its job, then the dryer acts like it's always on the highest setting.
From https://applianceassistant.com/Dryer-Repair/How-Electric-Dry... :
> The thermostat heater is often located within the cycling thermostat. However, it may sometimes be a separate component mounted to the dryer's cycling thermostat. Depending on the dryer's temperature setting, more or less voltage is supplied to this heater. Low settings supply more voltage and create more heat, while medium settings supply slightly less voltage, generating less heat. High heat settings will not energize the thermostat heater at all. In this way the thermostat is tricked into thinking that the dryer is hotter than it actually is, so it opens at a lower drum temperature.
https://www.energy.gov/eere/articles/no-heat-no-problem-ultr...
(Better not leave anything metallic in there though...)
The links to more detail with: > The goal of this project is to develop a clothes dryer prototype, using ultrasonic transducers, with an EF above 10 lb/kWh.
But also: > DOE’s Building Technologies Office is seeking new clothes dryer technologies that can increase the energy factor (EF) from 3.7 to 5.43 lb/kWh
However, a quick Google shows that the 3.7 is not a heat pump dryer, see e.g. https://www.intechopen.com/books/current-drying-processes/th.... The figure for an existing dryer should be 7.6 lb/kWh. Meaning, the solution is (currently) not good enough.
The link in the article and my link shows that the intend is to go way over 10 lb/kWh. The link I found showed it could be around 20 or even 44 lb/kWh (seems to depend on the frequency used). This while being way quicker than anything else, especially heat pump dryers.
Unfortunately doesn't work quite as well with clothing. Or perhaps I could make an analogy that lingerie is like a good knife?
[0] Stolen from somewhere online and can't be bothered to find the original source.
I'm washing t-shirts in 40 deg and drying them in my washing machine with built-in dryer.
They come out a bit damp to avoid creasing too much. I never had them smell even though I was just unloading dryer into a huge pile of damp clothes and leaving them like that for a day or two to dry out completely. I even forgot to take them out of the washing mashine and found out few days later. They were still damp but didn't smell. I washed and dried them again though to be on the safe side.
This stuff lasts forever when washed on cool/warm and then hung.
Friends of mine have complained about one brand or another not lasting very long, but they've been tossing the stuff in the drier.
We're fortunate to have a basement with a nice beam I can place hangers on (for winter drying), or a hanging bar I fitted in the garage (for summer). Lately I've been getting rid of 8-10 year old stuff that I no longer like or no longer fits, and it's sellable, as opposed to just worn out.
(Doesn't sell for much, but folks will happily pay $20 - $30 for special print cycling jerseys that are still in good shape and cost $80-130 new. Way better than tossing them in the trash.)
Always button and zip your jeans, and if you're not in a hurry, cotton clothing seems to be less worn by friction in the dryer than by the high heat. I run a lot of my cotton knits through twice on permanent press instead of once on cotton. And I don't use dryer sheets. Dryer sheets keep your clothes from getting static cling when you have over-dried them, but over-drying them damages them. The static cling is a symptom that you shouldn't ignore.
What you want to do is pull your clothes out when there is just a hint of moisture in them. The air and the latent heat should be more than enough to suck out that last hint of dampness. And if one towel or pair of pants is still damp, nothing stops you from running them by themselves for a couple minutes while you fold the rest.
UV from the sun kills bacteria, and you want that on the side near your skin, and as a bonus the inside fades (UV again) but the outside doesn't. I have some t-shirts that are quite faded on the inside but still reasonable on the outside.
I read in some credible, non-technical publication, I think the NYT or WSJ, an interview with a engineer in that field (something like detergents or washing machines) who said that detergents used to need heat to enhance the chemical reaction, but that it's no longer true and cold water works just as well.
EDIT: Does anyone know a good technical, authoritative resource on laundry? Consumer Reports has well-researched info, but not in the depth I'd like.
So a 40°C cloth can be washed at any lower temp but might deform or loose color or even breakdown if washed warmer than that.
> "Front-loaders and high-efficiency top-loaders run normal cycles 10 percent cooler than agitator washers, and the 'warm' wash temperature in the U.S. has declined by 15 degrees over the past 15 years," says Tracey Long, communications manager for P&G's fabric care products in North America. “Traditional detergent enzymes can be sluggish in cold water so we worked to create a mix of surfactants and enzymes that deliver cleaning performance in cold water across all product lines," says Long.
> Consumer Reports’ past tests found detergents have gotten much better at putting enzymes to work in removing dirt and stains at lower water temperatures, and are less effective at higher temperatures.
Source: Consumer Reports, "Don't Bother Using Hot Water to Wash Your Laundry: Consumer Reports' experts say cold water can get the job done", https://www.consumerreports.org/washing-machines/dont-bother...
If you want to sanitize anything, just use some bleach. It's harsh on fabric, but so is hot water, and the bleach will do a much better job. (FYI, I don't have any whites at all.)
> When a family member is sick, use hot water mixed with chlorine bleach to reduce bacteria in the bed linens and towels. The same goes for cleaning dirty cloth diapers, or other messes.
But also,
> Heating water accounts for about 90 percent of the energy needed to run a washer
So I only use heat for special occasions.
Article: https://www.consumerreports.org/washing-machines/dont-bother...
(This might even help deal with the continually scummy front-loader problem, but I can't speak to that as we prefer our 33-year-old Kenmore top loaders that can still actually be repaired rather than replaced with expensive new Chinese/Korean crap every few years. Mechanical timer controls and durable design and mfg FTW! For what it's worth, our total cost of purchase and repairs over 33 years is maybe $1200.00 for the washer/dryer set.)
I've bought an expensive front loading washer-dryer with water heater (upto 60C) and heat pump dryer recently. Now I always wash with at least 15C water, even 15C, it's significant difference in cold winter situation.
Symbols that you never use aren't very useful when all you really need to know is "do not dry", "do not bleach", "wash with like colors". It's really not that big of a deal to put a tag written in English and Spanish to the US, or in French to France, etc.
When artists use English, CAD designers use Traditional Chinese, and factory staff use Simplified Chinese or Vietnamese, and consumers use every language - there's a need for a standard symbol. You have a good point about dry cleaning services too!
The difficult part is that the people through this international supply chain can't type these symbols in emails, or search for them in databases. That's why a Unicode code point should be assigned.
This article looks like it has a general summary:
https://sewport.com/tips-on-starting-a-clothing-line-from-43...
This is not her company, but a job description for a similar role (you'll need to translate from Chinese):
https://www.104.com.tw/job/5cuv8?jobsource=jolist_c_relevanc...
I'm with you, it bears uncanny parallels to the PCB design workflow. Not just the Gerbers, but the component/fabric selection, simulation, design drawings, etc.
On the other hand, if the text was just in a language that I did not speak, I can either type this into a translation app myself, or use the automatic translation camera on my phone to identify them.
And sure, I can apparently now do that for those washing symbols too, which is nice... but why is that information being conveyed in a "language" that almost no-one speaks? I'd be just as confused if every item of clothing I purchased had washing instructions in Lojban.
I fully understand why an attempt at standardised symbols was made, being able to communicate that information more compactly would be useful, but it very clearly failed. They're not intuitive enough to learn without third-party resources, and a very very tiny fraction of the population is willing to put in the effort to do so. Just use text.
They are like traffic lights.
Oh and I guess just by normal kid clothes (cotton/polyester) so they don't have special instructions.
I wonder about helping manufacturers generate a QR code to use alongside the symbols to provide a detailed per-label translation?
Sounds like a failure of the point of those symbols. How about using words instead? Then you don't need an app to decode them. You can use google translate if you must.
It's a serious question. As far as I can tell, going by my wardrobe, there isn't. It's always been one of the minor annoyances in my life - clothing and clothing-adjacent vendors put these icons on their products, and I have no first clue what they mean, because which family of signs is used seems to depend on some combination of country of origin, target market, and the position of Saturn relative to Jupiter.
The rest of us learn from our parents. Or books. Or even Wikipedia.
Example: do not iron.
I remember doing some Internet searches for this over a decade ago, back when I started doing my own laundry :). Maybe I didn't look thoroughly enough - but between that search and the actual labels on the clothes I had, I saw no indication of a standard.
Might be because my clothes were probably a mix of branded things sold on EU market, and (mostly) unbranded ones I bought on a bazaar, which could've been imported from Turkey or East Asia.
Though I thought textile care symbols are common in US as well, or at least I think all my US-bought clothes have them too. So this is probably not one of those US-Europe differences.
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.
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.
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".
> 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.
ISO 3758:2012, Textiles — Care labelling code using symbols:
* https://www.iso.org/standard/42918.html
See also GB/T 8685, JIS L 0001:2014, ASTM D5489-96c, which are national versions that are basically the same as ISO:
* PDF: https://www.intertek.com/uploadedFiles/Intertek/Divisions/Co...
In case someone still finds this thread: standards my ass. Guess what, in Poland we have different ISO 3758:2012 symbols. Compare [0] with [1]. As it turns out, some of the symbols have "A" and "B" variant, and we use the "B" one for some reason.
Also I couldn't figure out WTF is "drip drying", and how "drip line drying" and "drip flat drying" differ from "line drying" and "flat drying". The Internet is very unhelpful here - every single article I saw assumed you already know what it means. Fortunately, [1] contained a note that the methods of drying are defined in ISO 6330:2000, and as luck would have it, I saw a copy of ISO 6330:2000 fall out of the back of a truck. Taking a quick peek, I now know that "drip line/flat drying" means...
...just "line/flat drying", except you set your washing machine to not do the final spinning cycle.
--
- [0] - EN ISO 3758:2012 :: http://labritex.com/wp-content/uploads/ISO-3758-Care-symbols...
- [1] - PN-EN ISO 3758:2012 :: https://www.eurowolle.pl/wp-content/uploads/2014/10/piktogra...
The standard is there. If people decide not to use it that's on them. Just because the US decides not to use the SI units, that says less about the metric system and more about the US.
Most countries in the EU (AFAICT) do use the ISO standard.
The fact that one country does not use it is not an argument that that standard is not a standard.
My point was slightly different. Poland does use the standard, the same standard. It just so happens that the standard has "B" variants for several icons.
I guess it's sort of an improvement that I only need to know 1.5 sets of icons instead of 3-5 different ones.
Some are quite important; like safety symbols.
One of my pet peeves has always been the difference between US emergency egress (“EXIT” signs), and everyone else in the world. In the US, they tend to be red, and the word “EXIT”. Everyone else does green, with the man running through the door.
In Japan, medical facilities were denoted by a green cross. In the US, it tends to be blue or red.
Color can be an important factor, but that’s tangential to the Unicode set.
Yeah, that could be interesting. I do know a lot of folks that think of weed/CBD as "Doc Stanley's Magic Elixir."
In France I've only really seen the green one for pharmacies but maybe I didn't pay attention.
Veterinarians don't seem to have any color code, that I know of. Many don't use crosses (they tend to have cutsey animals).
The hospital near where I live has a blue cross at its emergency entrance, and a nearby urgent care clinic also has a blue cross, however, another nearby urgent care facility has a red cross.
I don't know of any pharmacies that have any prominent cross displays. They tend to have their own branding (which may or may not have a cross integrated).
I don't know where this usage comes from (and can't really look it up now) but now that I think of it "the Red Cross" is a doctors organisation, so it fits the scheme I told about.
Wikipedia has a couple of symbols if you're curious: https://en.wikipedia.org/wiki/Pharmacy#Symbols
I suspect the OSHA (American safety standards org) requirement is a clear marking, and maybe a couple of choices.
You can buy the signs at almost any kind of general store.
But to totally wander down your tangent, color can be dangerous to rely on for accessibility reasons.
Green in particular, seems like a poor color choice for accessibility, given the prominence of red/green colorblindness.
I worked on an internal system with a Web UI once with someone much less sensitive to this than I was. He wasn't a jerk, just would do things and didn't like revisiting to change. I'm generally not a UI person and got tired of fussing about it, so just rolled with his "it's just internal" for his parts.
One of the things he made would highlight rows of text by changing the color from grey to red without any other visual indicator (bold, etc.). The grey text already annoyed me, but that's a different story.
Our very first user when we piloted just happened to be red/green colorblind and was completely confused. It didn't occur to him that color was the issue, and my coworker didn't understand why he couldn't differentiate. It dawned on me to tell him that the selections were red, and ask if he was colorblind. We walked through the rest of it with him and found another place where red and green text were used to indicate "good" and "bad".
A week later, my coworker took colorblind-support as a 'requirement' and had reworked everything he did to ensure multiple visual cues. When he did decide to fix something, he was very thorough. And I'm sure he carried this forward to everything he's done since.
I'm not an expert, but I think the red/green issue is the most common (especially for men), but I know there are other varieties, and other vision problems can make color difficult.
I think that the figure running through the door is a great example of a good symbol, though. No reliance on language and an easily identifiable shape. But I'm definitely not an expert in either accessibility or design. I just try my best at both when I have to do that stuff.
I use Sim-Daltonism[0] a lot. It's awesome.
For instance, while messing around with setting up the i3/Sway bar, I couldn't find symbols for:
* WiFi. Really. There's U+1F4F6, but it's not exactly the right thing.
* Anything to indicate CPU usage, like some sort of microprocessor chip.
* Anything to indicate RAM usage.
This is curious because for instance U+1F50A and U+1F507 exist, so you'd expect to have a set of such generally useful icons. Plus, it's computer tech. The lack of computer related stuff is odd, given that there's no lack of many things I have no idea what they're good for, such as U+1F574 ("Man in business suit levitating")
Edit: would be nice to have unicode support on here. Seems it gets stripped.
https://www.fileformat.info/info/unicode/block/miscellaneous...
And Unicode in particular has loads of non-letter symbols in it. It's only natural, given that a lot of these often show up in line with regular letters. Think of various paper documents you read, like instruction manuals, which make heavy use of non-letter glyphs in text.
It looks like this character made it into Unicode due to the fact that it was part of the Webdings typeface. Given how widespread that was, many of its characters made their way into Unicode.
https://codepoints.net/U+1F574
Now what it's original intent was, I'm not sure.
Of course. What could be more useful or obvious?
It’s not about “what could be handy” but about what is needed to cover character encoding already in broad usage.
Japan was early adopter of cellphone internet. One way to save data usage was to compose graphics as characters in a proprietary encoding (specific to the carrier!)
Basically, in order to move Japanese handsets of custom encodings and onto Unicode compatible systems, Unicode needs to be able to display not just all the Japanese characters but also the weird graphics that carriers decided to come up with in order to decorate their online services. This is also why there is so much Japanese food characters.
That isn't true anymore though, is it? At least Emoji seem like a case where inclusion precedes use and noth the other way around.
[1] https://www.unicode.org/L2/L2019/19068r-powerline-syms.pdf
Would you consider this to be a very different thing from, say, a MiniDisc? Yet there is an Emoji for that.
Obviously we cannot include every picture possible in Unicode, but there certainly seems to be demand for a lot of them. Besides really enjoying their use in texting, I've also come across a lot of professional uses as well.
Yes, this means that the Unicode Consortium probably has needed to adapt their original mission a bit, but I don't see the harm in that.
MiniDisc makes sense for two reasons. First, because it's a legacy inclusion. Second, because absolutely, you might use it in a text message. "Don't forget to bring over your bitchin collection of [MiniDisc] on Thursday!"
This is an important point that most technical people miss. They want to turn Unicode into a cross-platform FontAwesome. That's not what it's for.
There are a lot of specific-use symbols in Unicode (chess pieces, for example), but those are legacy inclusions because many of those symbols were included in computers before the internet.
I think that's also a distinction often missing in technical people's assumptions about Unicode and why it isn't just a cross-platform "FontAwesome" even just of legacy proto-FontAwesomes like Wingdings (which is also included and is its own different story). Unicode Consortium likes proposals to include things such as scanned documents of "here's how this 1850s book used chess symbols in the flow of text to communicate how the game is played". Not as adornments or images or separate figures, but directly as a part of the text.
That was one of the things that the Power Symbol Proposal [1] that was heavily discussed on HN in the past (and sort of spun out of HN comments in the first place) wound up learning and realizing how big that was to Unicode Consortium's needs in a proposal. "How was this used in real examples in the flow of text?" Finding and being able to cite and scan real world examples from text books and help documentation is an important part of the process. Even the chess pieces were about communicating to other people, in the flow of text in historic books and magazine articles and discussions.
Things like half stars was added by petition similar to TFA, so my post should have been more nuanced.
The point is that the reason why there is a seemingly useless emoji and not the [insert character you really want] is usually because one is preexisting and the other isn’t.
Japanese feature phone market was weaponizing lack of emoji support in modern smartphones to chase them out, but iPhone happened anyway and Apple started incorporating their own fragmenting SoftBank-iPhone-specific implementation into iOS so Google pushed it all to Unicode to fix them all up. They wanted to capture user emails into Gmail, and all emojis sent from featurephones being replaced with = by gateways was problematic.
1: https://blog.emojipedia.org/apples-emoji-evolution-1997-2018...
Emoji yes, the new emoji we get in annual Unicode updates, not...
1. Some large-userbase OS+messaging services provider, like Apple or Microsoft, sends a “proposal” for some new codepoints to the Unicode Consortium. The explicit message is “do you think these are worth standardizing?” But the implicit message is more unilateral: “we’re giving you advance notice, that we’re planning on including this emoji in our fonts + supporting it in our messengers, whether you like it or not, and whether it’s inter-compatible with anyone else’s systems or not. If you don’t standardize it, we’ll encode it using the Private-Use Area.”
2. Given the Unicode Consortium’s goal of never having proprietary text bits flying around the Internet — and given these big service providers’ histories of running messaging services (e.g. MSN Messenger) that did use proprietary encodings for emoji, resulting in some lasting problems with digital archaeology — the Unicode Consortium feel pressured by this “proposal” to standardize the proposed emoji codepoints, whether they really think they’re “worth” being standardized or not.
3. The Consortium also then feel pressured to get a new standard revision out quickly, to get ahead of the planned usage by these service-providers (because that usage would have to be encoded somehow, and if they don’t give the service-provider a codepoint to use by the time they ship their new font version that includes the relevant emoji, they’ll just have to make up their own.) In most cases, the Unicode Consortium is reactive to existing usage, allowing them to judge whether there is real existing adoption of a symbol; but here, they have to be proactive, pushing out a standard that includes a codepoint before knowing whether anyone will use it.
As a result, you’ll see these large dumps of new emoji where Apple/Microsoft/Google/etc. just decided autocratically that the world needed some more emoji, and Unicode begrudgingly followed along. It’s like what happened when Unicode first absorbed the emoji codepoints of Japanese feature-phones; but happening just-in-time, one at a time. (If those Japanese feature-phone manufacturers kept introducing new emoji, they’d have had to absorb those just-in-time too.)
There’s a separate, much more sensible and deliberate process the Unicode Consortium goes through you’re a regular-sized actor who’s not attempting to strong-arm them, where you do tend to have to prove existing use in either analogue documents, or as part of some proprietary digital text format.
[1] https://www.unicode.org/L2/L2017/17206-emoji-and-vendors.pdf
I’m pretty unfamiliar with Unicode, and this is interesting to read about. What’s your take on something like Linear A being included?
The alternative is to just not have Egyptian hieroglyphs in Unicode. The phallus is a frequently used symbol in Middle Egyptian. Then again, what's there is half-assed. There are no joining characters, so nothing displays right. And while you'll probably have the characters you need most of the time if you're dealing with Old Egyptian or Late Egyptian texts, Serapis help you if you're working with Ptolemaic-period texts.
At least the situation is better than with cuneiform, where Unicode alone can't represent a text because the characters drastically vary over time and you need to make sure you're using the right font.
The fact, however, is that Unicode is not sufficient for scholars who use Egyptian hieroglyphs or cuneiform. For the former, most people seem to use JSesh. For the latter, line drawings + transliterations.
That ship has sailed years ago with new annual emoji additions...
And even if that was the case, "what could be handy" would still be a good thing for the Unicode standard bearers to also have in mind...
ETA: The proposal[2] has been revived recently, and in the committee meeting[3], they're clear that the blocker is legal.
[1] https://ipkitten.blogspot.com/2016/05/to-boldly-go-where-no-...
[2]: https://www.unicode.org/L2/L2020/20181-klingon.pdf
[3]: https://www.unicode.org/L2/L2020/20169-script-adhoc-rept.pdf
https://unicodepowersymbol.com/
https://news.ycombinator.com/item?id=21689894
I also discovered 11 Chinese characters for Hakka and Taiwanese, and wrote a proposal for getting those added. They were accepted, but are still waiting for the next batch of CJK Unified Ideographs to be released.
https://medium.com/@peterburkimsher/hakka-news-adding-11-uni...
https://www.unicode.org/L2/L2006/06268-ext-link.pdf
The reason seems to be that links are not a feature of a text document, they are part of a markup language, and therefore, it should be a feature of that language instead.
For HN, AFAIK, they deliberately strip emoji, but most Unicode work fine. ("私はひどい下痢です" should show up correctly)
> The context for usage is mark-up with links by default.
Getting emojis accepted is much easier.
The overall goal is to standardize symbols for communication, not building UIs. Everything you mentioned should be an SVG instead.
contrast that with the symbols in this proposal - the TEXTILE CARE SYMBOL WASHING TUB WITH SEVENTY DEGREES CELSIUS glyph means the same thing no matter where it's used.
I can help with that:
> WiFi
"WiFi"
> CPU
"CPU"
> RAM
"RAM"
Clear, unambiguous, in common usage.
icon - explanation of the icon in your native language
word - explanation of the word in your native language
? Consider that you can type the word into google and it'll define it for you.Do you have any evidence that laundry icons are more universally understood?
Good luck finding any place in the world without plenty of signs in latin script, at the very least.
Find someone in the world who can use a computer but doesn't know what the word WiFi is, but would recognize an icon for it he'd never seen before.
https://www.ginetex.net/userfiles/files/Textile_care_symbols...
The document you linked to says they are "protected under trademark law", not copyright.
I would guess they are "certification marks", which are a bit different from a normal trade mark like "Apple" or whatever.
Their web site says: "GINETEX IS AN INDEPENDENT NON-PROFIT ASSOCIATION UNDER FRENCH LAW". So I would hope the fees are not exorbitant. But who knows? It's an independent organisation. If it did turn evil, would the French government intervene?
Symbols may be trademarked but that is specifically for logos and is a different concern (eg fair use rules differ, intention is to avoid confusion not preserve IP, etc).
(You can make an exact riff off any font but if you code it from scratch it is ok.)
They are not likely to want to give an open license to the public via unicode that might result in incorrect labeling.
Obviously ASCII was insufficient as it only really had Latin characters. Providing a standard interchange for the world's languages is a noble goal.
But then (IMHO) Unicode went completely off the rails by trying to create a code point for every imagine symbol, including emoji. And now I guess textile care symbols.
All the while, it's missing (at least as of 2015) key characters in living languages [1], engaged in the highly controversial Han Unification [2] (interestingly, there are Latin/Cyrilic and other duplicates that there is no attempt to "unify" [3]) and implemented Unicode code point modifiers.
Emoji, in particular, seems to be a huge mistake (IMHO). Like... it's going to be constantly changing. What's wrong with hierarchical approaches that we've used for things like DNS? Create a Unicode code point for "emoji" and then the next code point is a completely different standard.
The goal of creating a code point for everything just seems... wrong. We already have >1M code points. In 100 years at this rate we're going to have 1B+ code points where 99.99% of them are never used.
Why can't we just solve the problem of expressing written languages and keep the rest to a different space?
[1]: https://modelviewculture.com/pieces/i-can-text-you-a-pile-of...
[2]: https://en.wikipedia.org/wiki/Han_unification#:~:text=Han%20....
[3]: https://en.wikipedia.org/wiki/Duplicate_characters_in_Unicod...
Nobody really cares about Han unification either. It's fine, especially since you can use variation selectors or specify the text language to get appropriate fonts.
Now I'm curious because Wikipedia mentions the Han group has "experts from North Korea"…
Emoji... not so much
Emoji were certainly written language prior to unicode, but their expansion is unquestionably political since there is no well-defined "natural expression" of emoji that don't exist yet. It doesn't help that their standard [0] on what qualifies for inclusion and what doesn't is very poor, especially this: "Already representable. Can the concept be represented by another emoji or sequence, even if the image is not exactly the same?"
Let's say I want an emoji for glass of water for example. There is already one for glass of milk: . Well, I could use or or maybe even by itself is good enough, so my proposal would not be accepted.
Plain symbols within text clearly belong in a font. Logos, on the other hand, are images, not characters. Icon fonts, which are somewhere in between, became popular for webdesign but seem to be falling out of favor again. What is the current "best practice" here?
I'm starting to think it would've made more sense to allow unicode to allow to embed small vector icons directly in the text format. Some kind of restricted SVG-like dialect that would be handled correctly by all unicode parsers and look the same everywhere.
This way anybody could design their own application specific icons and emojis, you could either allow free-form emojis or only whitelist site-approved variants. Think something like fontawesome, but it'd work anywhere you can put unicode text.
Sure, it would significantly increase the size of the text but is it usually a big problem? It would compress very well, and in my experience text storage is pretty negligible these days in most applications compared to images and videos.
Instead it seems that we need to allocate codepoints and ask people to create fonts for textile care symbols, and national dishes, and all sorts of sports, and...
Unicode folks are also feeling this pain and there have been multiple attempts to decouple the emoji business from Unicode: the closest to what you've described is the Coded Hashes of Arbitrary Images [1]. (The proposed encoding is wasteful but of course would have been improved if it were accepted.) Considering that the Unicode consortium is a consortium of vendors, this emoji business is suboptimal even for vendors. But there seems no particularly good way to efficiently and securely implement such mechanisms.
[1] https://www.unicode.org/L2/L2016/16105r-unicode-image-hash.p...
https://github.com/twitter/twemoji
Without this maintaining compatibility with all platforms is a nightmare.
Maybe that boat already sailed with emojis, though.
I think the main motivation for stuff like this is for people to feel good about having an impact on something like Unicode. I fail to see how this adds any value to Unicode.
PLD text PLU would produce a subscript and PLU text PLD would produce a superscript.
If you have time to kill, it's super interesting on how they decide which emojis to add.
https://github.com/Crissov/unicode-proposals/issues/
There's a rather whimsical one proposed called the Priest Emoji!
https://github.com/Crissov/unicode-proposals/issues/425
Instead of having proposals, why not just implement every thing/subject/object/symbol we can think of?
Of course that limitation is artificial, due to compatibility with UTF-16 and UCS-2. So Microsoft would likely block such a proposal, since they'd have to change how Windows does character encoding.
https://en.wikipedia.org/wiki/Unicode#Architecture_and_termi...
https://www.johndcook.com/blog/2019/09/02/number-of-possible...
As I don't think they would make it in the unicode standards soon, I've found the openmoji project very nice, it lets developers and designers use meanwhile.
I.e. use words instead. Words work just fine. Words can be looked up in a dictionary (or just type them into google).
Good luck googling a scribble.
Type them into Google's search box.
Well, funny thing --- the explanations on TFA are all in a language I can't read, so the words that "work just fine" mean less to me than a lot of those symbols do. But, the answer to your question is "35".
> Good luck googling a scribble.
Reverse image search? Google in fact provides just such a service. Realistically though, this is how you google a laundry symbol:
https://duckduckgo.com/?q=laundry+symbols&t=ffsb&ia=web
You seem quite upset about this subject, but I'm not really seeing what's got you up in arms. These symbols have been used for ages now. Check any laundry garment you own. Having them included in Unicode (rather than forcing the use of some specialized font) isn't going to make them suddenly show up more places in physical print (and, conversely, keeping them out of Unicode will not make them go away). On the other hand, if you're encountering them digitally (as Unicode), you can just copy/paste the glyph to search for it. It's literally implemented as text at that point.
> Words can be looked up in a dictionary
Why on earth is is acceptable to pull a dictionary off the shelf and page through it (or load up dictionary software, etc.), but not okay to consult a laundry reference (digital or otherwise; if digital, almost certainly found through Google)?
https://duckduckgo.com/?q=laundry+symbols&t=ffsb&ia=web
which involves knowing several English words, including "Laundry", but it is unreasonable to type:
define "word"
into google?> copy/paste the glyph
Yeah, right off of the laundry tag!
> Why on earth is is acceptable to pull a dictionary off the shelf and page through it (or load up dictionary software, etc.)
Bring up google and type:
define "word"Because icons make things pointlessly harder to use. Instead of teaching children 26 letters, do you want to burden them with learning thousands of "standard" icons in order to read?
Are you really helping tribes that have had no contact with the rest of the world?
As for Unicode, a boatload of these things gets invented and added to Unicode every year. Where does this stop? Do we really need an "alphabet" with a million symbols in it?
If you are drawing Unicode characters that include a full range of Emoticons, you are most likely using a platform API provided by Apple/Google/Microsoft or similar. You, like most developers, most likely live in "Big-tech land", so you get this for "free".
If you want to port your application to an open source platform or a new upstart platform, where this isn't available, they may not have the resources to draw thousands of Emoticons, so its harder for them to attract you as a developer.
Lets say someone is writing a SMS app for something like a PinePhone. SMS is open enough protocol that this is possible. The UI for a chat app is something you can build in fairly short order. There are plenty of open fonts, you can use, but there are no open fonts that have thousands of detailed and sometimes animated Emoticons. Without Emoticons very few people are going to want to use a PinePhone as their main communications device. The amount of effort needed to implement a SMS chat vs a SMS chat + draw all emoticons people use is massive.
Unicode, and SMS are both open, but given the size of the Unicode Spec, its effectively shutting out any small player form implementing it. Big tech gets to claim they use open standards, but at the same time make sure no one can threaten them.
Its a bit like when Microsoft tried to make a standard for documents so complicated that only word could implement it.
License a commercial font or use Twitter's CC-BY font: https://twemoji.twitter.com/
> Unicode, and SMS are both open, but given the size of the Unicode Spec, its effectively shutting out any small player form implementing it.
You only need to implement the Unicode spec if you want your own emoji designs.
You only need to implement glyphs people are actually using. If people are using [some glyphs] from the Unicode spec in your app, yes of course you need to use a font that implements them. How else could it possibly work? What would your alternative be?
I found a paper on it!
https://brenthecht.com/publications/cscw2018_emojiimpact.pdf
Unicode also packages an essential but (in hindsight) complex concept and process like "what is the word boundary" or "what are characters usable as a part of identifiers" into a neat algorithm and data table. The algorithm is more complex than the data, which is readily available for you. Assigning a new character to Unicode mostly means a change to that data, not to the algorithm. If you consider one should be able to display every assigned character as expected to be fully conforming to Unicode---I stress it's not true, but if we assume so---then there would be no conforming implementation of Unicode at all. All Unicode implementations just implement what they need to support.
[1] For example, the requirement C12 (https://www.unicode.org/versions/Unicode13.0.0/ch03.pdf#page...) specifies that you need to implement the Unicode Bidirectional algorithm only if you support right-to-left characters. In the other words you don't have to implement the Bidi algorithm for conformance.
What does an extra line added to an already existing icon mean?
I guess the main point is that they're already standardized.
Really, why is this a problem for people on HN?
I'm hoping it's not what I think it is.
I wonder how they did arrows before.
I wonder how they did musical symbols before.
I wonder how they did typesetting markers before.
I wonder how they did braille before.
Wash Care Symbols M54
The font Wash Care Symbols M54 has already implemented textile care symbols. However, they are encoded in the C0 Controls and Basic Latin block.
A font is just[0] a table that maps numbers to pictures. A typical font will map a number 65 to a picture of what we know as letter 'A' in Latin alphabet. But there's nothing preventing you from making a font that will contain, at index 65, a picture of a dog. Or a "hand washing" symbol. And this is what people did - both to support non-English alphabets in the era where "printable character" meant "7 bits", and to support mixing graphics with text (if you add that missing bit to make a full byte, you get 128 more codes to play with).
Ultimately, screens and printers don't understand letters - they understand arrays of color values (or, occasionally, colors attached to parameters of a curve). Fonts are the intermediary, and you can draw anything with text if you supply the right font. The problem is though, if you had a custom mapping of characters to pictures, you had to ship it with your text, and make sure users know how to configure their software to use your specific font for your text.
Unicode exists to allow every number describing a character to have a fixed, standardized meaning, so that you can send text around independently of the fonts. Instead of fighting for the same 256 codes, there are now over a million possible codes, and fonts declare which code ranges they know how to draw. As a result, you don't have to worry about mixing alphabets and graphics in text anymore - worst that can happen is that something will get rendered as a placeholder. But it won't get rendered as a wrong symbol.
--
[0] - Well, strongly simplifying. In reality, the "picture" can be anything from a bitmap, a set of bitmaps, a vector image, or executable code; the mapping part can also be executable code. A prime example of "code is data" :). Simple devices like thermal printers might accept only a trivial byte-to-bitmap mapping (aka. "bitmap fonts"). More complex ones will work with modern fonts, which are essentially programs that interpret text and produce instructions to draw it. Pushed to extreme, you get things like a videogame inside a font[1], or a font that automatically translates startup marketing copy into plain English[2].
> Symbols for salt, vitriol
would be useful for sure on HN!
Sure, it isn't technically as neat, but it gives far more flexibility. It happens already in memes (where text is usually part of a gif)
Text and text encoding dates back from the days when every byte of storage space mattered. Now lossless high resolution images are the norm, and wouldn't constrain what symbols could be included. If you want to make a word be slightly bendy for style, you can!
Accessibility, relayout, etc. can all be done with images too - you simply have a tool which extracts the text, transforms it however you please, and then puts it back as an image.
Now if we only had some way to figure out which image in the bundle corresponds to what... Maybe some encoding scheme where we assign a numeric ID to each image?
(Oh wait...)
- You can copy a text symbol and put it into a search engine to figure out what it means.
- Screen readers can recognize text symbols without needing an alt text.
- Text is more flexible on dark or light backgrounds and has better contrast.
- Text is better suited for virtual keyboards and auto-correct or auto-replacement.
- Text can be used in input fields.
- Text has native rendering hints built-in, such as baseline and kerning, which improves inline rendering.
- Text is more flexible when choosing a glyph. For example, you can render it larger for the visually impaired, or change fonts and put a special glyph into the font.
- Text is more flexible when choosing color vs. black-and-white output. Try printing an emoji to see what I mean.
For example you could take part of an image and put it into a search engine too... That search engine would take images as input, and where the image represents writing if some kind, it would return relevant results.
Screen readers could look into an image and read out any writing found, just like some screen readers can describe an image ("person in boat holding flag"). Deep nets that can do this reasonably well have been around years now.
Easy if there's a "do not iron" symbol in text to search. Much harder to grep if it's an image.
And how would the software that extracts text from an image store the extracted text? If it comes accross a number of symbols from different domains how would it save them, and what table of contents would it use as a reference? Unicode.
Then you still need some way to handle text, and image to text is not reliable. Text simply has so much more distilled information. Images are nice for humans, but I can't imagine them as a storage format for programs.
This is extremely non-simple. It is a strictly harder problem than just... encoding image+text in a sane container format like HTML or SVG.
However, that fact does not help you when you want to reply to my comment. Or more generally, if you want to edit, transform, store, compress, search.
I can easily search 1GB of text on my computer for a specific pattern. I could not even store all that information directly encoded as (say) raster or vector graphics.