Windows 11 calls a zip file a 'postcode file' in UK English
twitter.com
twitter.com
"He looked out over the apartment landscape"
and
"'Come with me', he said apartmently"
- "None of these were quite that bad – they were subtler..."
- "F’rinstance: All instances of the word round have become around. Fine for walking around the lake, less helpful for the around glasses, the around holes in the ice; blonde has uniformely become blond, and so blonder has become blondr; for ever has become, universally, forever, and for everything thus became foreverything, and we also got foreveryone, forevery time and so on. Each had to be found and caught."
- "Little things – the icelandic þú became bú, which won’t bother anyone who isn’t Icelandic. Blowjob had inexplicably become blow job again. (I think a blowjob is a unit of sexual currency, whereas a blow job is something you can get -- or indeed, give --instead of a wrist job, a sleeve job or a window job.) And once again every damn comma gets scrutinised. And I changed an Advertise to an advertize which was nice of me."
https://journal.neilgaiman.com/2001/03/ ("American Gods Blog, Post 24" [2001])
It's never stopped me from reading a book before, but it does diminish my enjoyment quite a bit. For nonfiction, I don't care, I'm reading actively regardless. But when reading passively for enjoyment, it's noticeable and irritating.
“Sophomore”, maybe?
(For those who can't read it - the text is English transliterated into Hebrew script, not actually Hebrew. I'm impressed that Google managed to make sense of it)
> И I struggled for a bit with this one, but I don't know of a better way to represent it other then "ai" in Cyrillic I guess.
The "ѵ" is interesting too, never seen that before since you can make do with the sorta B-looking letter instead.
No, never was a thing. Early Cyrillic had a bunch of unique letters that are long gone, but it never had "þ" in there.
> The "ѵ" is interesting too
It's from Greek "Y" (upsilon) and it - depending on the place - could've meant either /i/ or /v/ sound (and /u/ when in "оѵ" digraph, so parent comment has it wrong): https://en.wikipedia.org/wiki/Izhitsa
- instead þ could be used ѳ;
- с in тектс is missed, it should be текстс or better теѯтс;
- ѵ is basically Greek upsilon which appeared in English mostly as u [auto] or y [system], therefore шѵд would be better written as шоѵд where /oѵ/ in old Cyrillic pronounsed as /u/ as in Greek, or just шꙋд;
- дж in лангѵадж could be writtend as џ;
And so on.
If you want to see how it should look in context, here's a typical 17th century example: https://www.raptisrarebooks.com/images/86066/paradise-lost-a...
The prints from the 18th century are even nicer with better quality and consistency in general. The Caslon typefaces are pretty exemplary here: https://upload.wikimedia.org/wikipedia/commons/4/45/A_Specim...
Roman typefaces with a long-s are a very 17th-18th century thing. A blackletter (gothic) typeface gets you closer, but all of that is still not very much medieval. What you really want is a meticulously manuscript in Carolingian Miniscule[1] or Uncial script[2], complete with killer rabbits[3] and knights fighting snails[4].
[1] https://en.wikipedia.org/wiki/Carolingian_minuscule
[2] https://en.wikipedia.org/wiki/Uncial_script
[3] https://blogs.bl.uk/digitisedmanuscripts/2021/06/killer-rabb...
[4] https://blogs.bl.uk/digitisedmanuscripts/2013/09/knight-v-sn...
Upvoting because this is seriously interesting. I can see old or Tolkien English being a hurdle, so I relate to what you’re saying. But small changes in diction tend to draw me into the world, by othering it from the familiar.
But there are difficult examples, even in Rowling. She uses "revision" in a way that American readers don't know ("studying") and might have a hard time piecing together from context. It's not like the reader will be prompted to open a dictionary, since "revision" is a common word in AE. It just makes for a poor reader experience.
> Righto, mate, gimme a shout as Ishmael. Few donkey's years ago—don't get your knickers in a twist 'bout when exactly—findin' me wallet as dry as a dead dingo's donger, and not a bloody thing worth a squiz on the land, reckon I'd chuck a U-ey on life, put a bit of water under me bridge. Wanted a stickybeak at the wet half of this great wide world, didn't I?
(With ChatGPT assist!)
- can’t hear the differences in spelling between American and British English
- are listening to someone read. That person probably is able to read either American or British English.
That said, some words really are different and could cause confusion/disconnect so probably are potential candidates for being changed even in audio books.
- the one he gave “apartment” vs “flat” is a good example. I think British people would all be fine with “apartment” whereas I think “flat” might confuse some Americans who hadn’t heard that usage.
- “pavement” means the road surface in the US vs it means the pedestrian path on the side of the road in the UK (that in the US you would call a “sidewalk”). “Sidewalk” wouldn’t confuse a British person but it’s not a word a British person would use. “Pavement” meaning the road surface does confuse British people.
- “jumper” in the UK vs “sweater” in the US
- Don’t even ask about “pants”
- etc
On the flipside, I was delighted to hear stories of US kids confusing their parents with British English because they'd watched so much Peppa Pig during lockdown. Very good.
Imagine learning something about the world after reading (or hearing) a book!
Don't know why someone would "rent a flat?" You go look the phrase up and discover that it's British usage. Confusion over... because you learned. Reading Moby Dick and don't know what "scraggy scoria" is? You look the words up and learn they're the perfect fit for the landscape Melville is painting.
But here's an example that's worth thinking through. This movie https://www.imdb.com/title/tt0110428/?ref_=fn_al_tt_1 was called "The Madness of King George". It's based on a play called "The Madness of George III". They changed the name when producing the movie because of the difference between Britain and the US.
In Britain pretty much everyone would know that George III refers to King George III. However when they first started discussing this project in the US, a common reaction was "I haven't seen "The Madness of George 1 and 2". Now the differences between the titles wasn't that important and clearly this was just an impediment to understanding with no benefit.
Now you could say "Well the people could go on wikipedia and find out that there was a King George and a King George II and then this guy, George III" and that's true but the problem is negative self-selection. People who don't know that don't realise that's what's at play here and so won't do that search so nobody learns anything.
and then run this prompt on each pair of words that you want it to do. When it's done, run a quick diffcheck on it & check its work to learn of any gotchas.
That said, I found myself doing little text mangling tasks with GPT-4 instead of appropriate command line tools, because fuck if I remember the flags to sort and unique, and it's much faster to just describe what I want and have the LLM take a crack at it.
This is why, I think, you'll see a lot of simple(ish) tasks being done by LLMs, at couple orders of magnitude more compute cost - it's just that much more convenient.
EDIT: nevermind. That was about just doing regex replace.
But if you want to do it correctly in an automated way, LLMs are indeed the best tool for the job in the general case, because they understand how language work, in a way that you can't really formalize in code. No, feeding the complete definition of English grammar to the computer won't help, because a) it probably doesn't exist, and b) even if it does, it's merely a suggestion - natural language is a living thing, and is not bound by fixed rulesets.
"Oh, I live near there too! House or flat?"
Stanley hesitated. These questions were getting more and more personal. Was this her idea of casual conversation? Or was she trying to get to know him personally? Well, he thought, what could go wrong if I treat this like a conversation. "Flat," he said. And then asked a question of his own. "What kind of pop do you like?"
How are you going to decide if "flat" is talking about non-fizzy pop/soda, or a dwelling space with a regex? It's a lot closer to the word "pop."
Of course, GPT handles this perfectly https://chat.openai.com/share/fb6a56a2-749c-4e71-9506-541bb8...
But I'll admit I agree that this is well beyond the scope of regex.
Are we really going to let big corp automate away their role in the social contract? Ostensibly Random House needs to provide real output not just be a brand that farms out all the work to AI, and thus captures value on the fiat ledger.
The number of rent seeker non-contributors is too damn high. We cannot base society off dying peoples hallucinations about how the world works anymore. This is bonkers.
I never asked to exist. Why am I constrained to beliefs like Bill Gates and the like are divine in contemporary ways?
Suddenly, we had a lot of "switch/task" statements that somewhat perplexed the compiler.
It was a British company.
Cultural hegemony complete.
I foolishly expected that people like Elon Musk could be truthfully called "African-American", but I did a survey of the definitions, and most all of them agreed that an African-American must be Black (and I'm not sure how that is recursively defined, or whether it has to do with race, ethnicity, or simply color of skin: it must be the latter if it has any meaning separate from "African"!)
American: "I'm Irish" Me: "No, you're not"
They gained American citizenship. She became my African American friend. Everyone told me I was terrible for talking that way.
Had to explain to her why it would not be good idea to do that in the US.
I never believed in the idea of embracing an offensive word and somehow "taking out the sting" like rappers did.
We have a similiar word - the k word for blacks - it is fortunaly banned and if you used it on social media you clearly identify as a racist.
The change from "black tie" to "african-american tie" seems much less like a goofy 'find and replace' fail when you read it that way.
In my experience Americans are shocked that it's perfectly fine to say that someone's black in the UK.
One positive outcome though is the invention of a collection of excellent words: foreverything, foreveryone and forevery. I don't know what they mean, but I like them.
Ah, the Scunthorpe problem. [0] It's never a good idea, but the immature 12 y/o in my always giggles at the examples.
One of my favorites is the word "ass" being replaced by "butt", resulting in this gem [1]...
"'Prohibition on buttbuttination' states, 'No employee of the United States government shall engage in, or conspire to engage in, political buttbuttination.'"
[0] https://en.wikipedia.org/wiki/Scunthorpe_problem#cite_note-b...
[1]
So the BBC was allowed to register their domain without issue, but Craig couldn't register his account with the BBC. That's Dick.
"It was about 1000 feet, or 304.88 meters". "He was 6 feet tall, or 182.88" meters."
Every single measurement, converted with two or three decimal places. It got old fast.
The Norwegian subtitle? 'Do you know where in Gettysburg Lincoln lived?'
Oh, and of course, from Star Wars - 'Luke, this is your father's light sabre' was translated as 'Luke, this is your father's lightweight sabre'
[0] https://en.wikipedia.org/wiki/What%27s_Up,_Tiger_Lily%3F
So a Norwegian interpreter - who has no obligation to know of Lincoln whatsoever - can read it and reasonably interpret it as a request for an address in Gettysburg, for Mr Lincoln.
Part of being a decent translator is having a knowledge of the common cultural references of the source-language’s country/countries. Films very frequently generally play on local history or previous films or literature, and you are expected to be able to deal with that.
Do you seriously not know that a speech is an "address?"
that was the entire point of the comment
A few years after I saw this, I entered the film translation business myself. Generally for anything Hollywood or otherwise big-budget, you can watch a copy of the whole film yourself to understand the context, and you can bill the client for the time spent doing that. Therefore, I tend to suspect that such cases of mistranslation are laziness or a company with an incompetent workflow.
Putting this here for anyone who needs a laugh:
Star War The Third Gathers: Backstroke of the West: https://www.youtube.com/watch?v=9DI5WyiHQno
(Someone took a copy of Revenge of the Sith that had been translated from English to Chinese and back, and then re-recorded that dialogue and put it back over the original footage.)
(Baader-Meinhof is a funny thing. I have learned of this movie less than 12 hours ago and here it is again)
I'm amazed by how much more realistic the space fights looked in the first three Star Wars movies compared to the CG stuff.
http://winterson.com/2005/06/episode-iii-backstroke-of-west....
It was originally bought from a DVD street vendor in Shanghai. And it's the source of "do not want" as a meme!
> I have to stop and think if I need to translate [] to American.
and I assume (reasonably though not certainly) that the commentor is not Sumerian.
https://www.livsmedelsverket.se/en/food-and-content/oonskade...
Go figure.
This translation really is weird! :-D
Of course, exactly 6 ft is 182.88 cm, but the precision is unnecessary there too. 189 cm if it was right on the 6 ft mark.
I get lots of advice like that regarding code and UI and the suggestions about perspective problems are often absurd. Nobody has been confused by the thing yet and they're concerned that someone "might" be confused and not able to figure it out themselves so they change some words or UI and ... I kid you not more often than not the solution is the thing that trips up users.
In the above example, maybe if the reader doesn't know what a "flat" is, maybe they'll just look it up or understand by context and they'll be ok?
Having said that, I don’t disagree with what you’re saying.
Change all occurrences of flat to apartment, intelligently!
Got you!
;-)
Ch(e)ating, obviously. You omitted apartment in the replacement.
> echo "wikings" | sed "s;wiki;encyclo;" # which is what enci.ru did
"encyclongs"
> One general point. A thing I have had said to me over and over again whenever I’ve done public appearances and readings and so on in the States is this: Please don’t let anyone Americanise it! We like it the way it is!
> There are some changes in the script that simply don’t make sense. Arthur Dent is English, the setting is England, and has been in every single manifestation of The Hitchhiker's Guide to the Galaxy ever. The ‘Horse and Groom’ pub that Arthur and Ford go to is an English pub, the ‘pounds’ they pay with are English (but make it twenty pounds rather than five – inflation). So why suddenly ‘Newark’ instead of ‘Rickmansworth’? And ‘Bloomingdales’ instead of ‘Marks & Spencer’? The fact that Rickmansworth is not within the continental United States doesn’t mean that it doesn’t exist! American audiences do not need to feel disturbed by the notion that places do exist outside the US or that people might suddenly refer to them in works of fiction.
https://news.lettersofnote.com/p/please-dont-let-anyone-amer...
I did not know at the time what an analgesic was, despite having a fairly broad vocabulary. If anything, I assumed it was some dirty adult toy; certainly not a thing to be consumed as a remedy for pain.
It was frustrating because I searched high and low for aspirin, Tylenol, pain-killer, etc. but never got past that section until I had a chance to search the Internet for a solution - many years after I really cared to play a text adventure again.
Newark (on Trent) is in Notts. Rickmansworth is pronounced "Rick-uth" (not really but it should be) and Bloomingdales would be pronounced something like "Blimmin'dolls", if it ever showed itself over here.
The Adams quotes are from some time ago and we have all passed a lot of water since then. The entirety of en_* are now routinely bombarded with everyone else's TV/stream output in various guises. I might be a Brit but I am now (not really) intimately familiar with Australian and New Zealand police and "Border Force" etiquette and more. I can even hold my own when confronted with a particularly tricky issue in say Nunavut with the RCMPs. I am of course an expert in Texan rangering thanks to a bloke called Walker.
You say tomato and I say fuck that: viva la difference!
I would be surprised if they were recent, but I wouldn't put it past him, either.
https://hitchhikers.fandom.com/wiki/Rory_Award
Definitely funnier as “Belgium”.
Resulting in such lines as "The tower can take up to 200 points of dawizard before it is destroyed. Dawizard sustained is cumulative." and references to a spell called "Silent Iwizard".
[1] - https://www.reddit.com/r/DnD/comments/s82mi4/til_that_in_199...
[1]: https://github.com/DaveJarvis/keenwrite
[2]: https://youtu.be/CFCqe3A5dFg?list=PLB-WIt1cZYLm1MMx2FBG9KWzP...
Ha, so yeah it seems like that's definitely a part of it.
America is "Měiguó" in Chinese.
I'm pretty sure the Chinese decide for themselves what they want to call America.
Imagine if I asked you what your name was then ignored what you said and pronounced that I would be called you Frank. That would be quite rude.
Von den Germanen.
https://en.wikipedia.org/wiki/Germanic_peoples
I'm not a fan of this modern idea that you should get to dictate how others refer to you. E.g. I don't think it makes sense to refer to China as Middle Country for anyone not from China.
Turkey isn't rude, and it's usually understood from context that we don't refer to the bird (the Turkish government also push Türkiye on countries where the native word has no bird connotation). We used to translate all names, and that's understandable because names are often unpronounceable or otherwise violate grammatical rules if you just blindly drop them in a different language. I think it should be fine to use "Turkey" when talking to another English-speaker.
Normally, I'm outspoken against most "domestic" proposals to change words, since the rationale and implementation are usually very poor.
But as an American, I've decided that Turkiye without the ü is more desirable than Turkey. It resolves an annoyingly ambiguous search term, doesn't change anything about how it's pronounced, reads the exact same way, and it's trivial to switch how I write it. It really is a superior design with a painless transition.
Another issue I've had in newest file explorer, (probably a bug, unless they're trying to get rid of ".txt" files), is this one also reported on Twitter by "MittringMartin":
https://twitter.com/MittringMartin/status/166378202005572812...
can't do "right click" > "New" > "Text document".
Happens on my system too, a stock windows install on a surface laptop, for which I've never messed around with any obscure settings.
It's also gone from the "shift right click" menu (aka the good old menu)...
1. Historically it used to contain a bunch of blank file types, including .txt files.
2. Now it only has a Folder, Shortcut, WinRAR archive. That's right, only three items. This has to be a bug.
Yes. I've used 7-Zip some, earlier, and found it to be quite good. IIRC, from both command-line and GUI.
It's a very solid archival program. I wouldn't recommend that everyone runs out and buys it, and I use 7zip more than Winrar, but it does have some advantages, especially on Windows.
Like the one that 7zip has AES256 encryption and WinRar can't open it, that one?
In windows, when you extract a zip file that contains japanese characters, they get 'garbled', which can cause problems if you need to maintain the directory and file names. I tried with 7-Zip as well with the same outcome.
I found a fix on stackoverflow [1] which mentioned using winrar, as it had an option to change the name encoding for archived file names. Using that I was able to extract the zip and the files and directories maintained their original japanese names.
[1] - https://superuser.com/questions/554108/extracting-a-zip-file...
I did not look it very closely so I don't know what exactly infozip was getting incorrect in my case. but I did find this interesting bug report from 2012. Apparently a lot of encoders are sloppy about the spec and will leave header fields zeroed rather than set them. and if infozip reads a header that says the zipfile was created by dos(a zero) it believes it and extracts it using a dos compatible encoding.
I'd say whatever it is, it's been happening for a looong time, considering they've still never fixed the glaring bug in previous versions where the down arrow takes you to the second file in the list. Or where you go to save a file (save as), and you put your cursor at the end of the file name to rename just part of it, the cursor randomly-but-not-always jumps to the beginning of the file.
Every once in a while, navigating with the keyboard in Explorer will cause the window thread to hang up in a busy loop and I have to kill it. I have no idea if this is an Explorer bug or caused by other stuff.
They've saved a boatload of money by offshoring this work.
They spent all their creative and time budget on implementing the new explorer tabbed interface :D
Why could he just heard for Notepad in the start menu and open it there? Rather than going through the process of gutting out a publisher file.
- "The name "zip" (meaning "move at high speed") was suggested by [Phil] Katz's friend, Robert Mahoney.[4]. They wanted to imply that their product would be faster than ARC and other compression formats of the time.[4]"
"What should I give my sister for unzipping?"
"20 bucks?"
"no like, for files and stuff"
They needed a new compress/decompress tool once IBM asserted their patent rights on the LZW algorithm used in the compress tool.
zip uses a different header for the compression stream, commonly known as the zlib format.
They also use different checksums at the end (CRC32 vs Adler32).
Also it should be Gzip, not gzip, although it's not ambiguous since the reciprocal prefix is nano-, and in general there are no 2^-X0 prefixes that start with g- like there is for Mega-/milli-.
kilometer = 1000 meters
The term ZIP is an acronym for Zone Improvement Plan; it was chosen to suggest that the mail travels more efficiently and quickly (zipping along) when senders use the code in the postal address.
And what options are available when I right click on a .zip/.postcode file? Say, perhaps I wished to uncompress it?
I don't remember exact occurrences but I've noticed quite a few similar problems on macOS that are just the result of words being translated out of context.
On a popular forum software I used to do support for, "flag" (for moderation) was translated in French as "drapeau" for example. Which is technically correct I suppose, drapeau does mean flag, but the wavy kind of flag that countries like to use as symbols. Nothing else. And it's not a verb.
In this case, there is simply the string "zip" somewhere that is used both in some address forms and for the file type, and the translator just happened to translate the first occurrence probably without even knowing that is was also used in another context as well. Or without any means to ask the dev team to separate them into two terms. Which might not even be possible if they used too simplistic a translation system.
Translators usually just get to see the string they are translatinbg, and if they're lucky a 1 sentence explanation written by a programmer.
With no context, a "Zip file" might indeed mean a "postcode file" - perhaps it is a file for storing all the zip codes, and now it will be used for storing all the postcodes?
It doesn't help that a lot of developers probably never translated an application; when I added translations the first thing I did was translate it myself, but that's not really feasible for larger systems and/or with people who don't speak a second language well enough to actually do translations.
https://media.discordapp.net/attachments/323831494718128130/...
This is French, English, German and JavaScript all in one sentence.
Two trillion dollar company.
So, you have to understand 2 languages to understand these listings.
Oh yes, the classic "I just picked the string from my IDE's dropdown list, it was there so it's fine right?"
Your programming language reserved keywords changing depending on your selected language was a big facepalm.
Searching for this problem on the web doesn't produce any valid relevant results, so the web has forgotten or maybe the horror has been plastered over.
I remember seeing the dictionary to translate between German and English function names[1], one time I googled for "Excel German translation" and Google proudly showed the Translate interace pre-filled with "English: excel / German: übertreffen"
[1] https://www.perfectxl.com/excel-glossary/what-is-excel-funct...
Where it went wrong is that as soon as you choose a language you were stuck with that. It should have been a display option.
=CERCA.VERT(B2;C2:E7;3;VERO)
[0] https://support.microsoft.com/it-it/office/cercare-valori-co... Nej.
1
2
i18n is HARD. But it's not THIS step that is hard. This is day one of i18n school. You can't translate from english terms. Just stop translating things from english, translate from a neutral key! key en-US sv-SE
num_short "No." "No."
yesno_no "No" "Nej"
yesno_yes "Yes" "Ja"("Hillbillies" not meant derogatorily.)
I remember one z/OS manual saying AIX stood for “Advanced Interactive eXecutive”-which is true if we are talking about the Unix, but this manual was talking about a VSAM AIX (Alternative IndeX) - a secondary index for the VSAM flat file database system. Another example was USS being wrongly expanded as “UNIX System Services” when in the context it was actually a reference to VTAM’s “Unformatted System Services” (the part of VTAM which handles the initial LOGIN command, I think “Unformatted” because it is plain EBCDIC not 3270)
In Windows, there is an account flag called “UF_MNS_LOGON_ACCOUNT”. A lot of people claim “MNS” stands for “Majority Node Set” - even one MS doc - see MNSLogonAccount in https://learn.microsoft.com/en-us/powershell/module/activedi... - however, while it is true that’s what the acronym stands for in the context of Windows clustering, I’m pretty sure in the context of Windows user accounts it actually means “Microsoft Netware Services”-this flag was used by Microsoft’s 1990s era software which enabled Windows NT to pretend to be a Netware server, and the unrelated Windows clustering “MNS” has never used that account flag. “Microsoft Netware Services” was renamed to “Microsoft Services for Netware” (MSN-but not that MSN!-hence MSFN or SNW), no doubt for trademark law reasons, but the name of this flag got stuck with the original acronym. I don’t think it actually does anything unless you have that old stuff installed, which probably doesn’t work on newer versions of Windows. I suppose that being an effectively disused flag, there is nothing stopping people from stealing it for their own purposes, and probably someone out there has.
Same day delivery online before Amazon started doing it with Prime Now too.
Their app update release notes used to be hilarious too but they've stopped doing them, I think the person responsible left. https://thecircular.org/argoss-hilarious-app-updates/
I’ve found that often when my fellow Brits complain of a word being American it’s actually just an old English word we stopped using.
Even rather light industry. Coffee grinders have a feed hopper.
(If anyone has this British English Windows 11, is it still the Recycle Bin, or the more British Recycling Bin?)
* "Recycling Bins" from Home Depot
* "Recycling Bins" from Amazon
* "Find the Recycle Bin" from Microsoft
* "Recycling Bins" from Lowes.com
* "Recycle Bins" from Target
* "Recycling Bins" from Walmart
Do they also localize the folder path? It’s “./Trash” in US english
It's still internally .Trash, as that isn't user visible I suspect it's the same for all localisations of Mac OS.
Please always remember to let your users change regional settings separately and individually for currency, measures, first day of the week, etc.
As a Brit, I think it's a tad unfair on the yanks to see them as that parochial. As a test, ask any Brit moaning about the NHS and railing against the US private system (these complaints often come together from people who would never consider themselves parochial) whether the health services of Germany, France or the Netherlands are private. They won't have the first clue.
Just shows you, all that consumption of worldly and international news by worldly and international types remains strangely parochial, and that's just one example.
Now, they're thought of as American.
Also, more vague but fascinating, is that the American "southern accent" (quotes because there isn't a single southern accent, but most people think of a specific one when they think "southern accent") is largely a "British accent" (quotes for the same reason), but British circa the 1700s.
This is actually a fascinating subject, well worth looking into if you're interested in English language history. Also interesting is that the division between American and British English has been growing softer over time, and more and more modern Britishisms are being used regularly by Americans (and vice versa).
The various accents do tend to have features in common, though, so you can hear that the various southern accents are part of the same family, and similarly with the various British accents. There are, of course, exceptions to this as well. This bit of linguistic history is really referring to a fairly specific American accent and a fairly specific British accent.
The Southern accent in the US did not emerge until after the Civil War, replacing a diverse array of local accents. It came from the Appalachian South which was settled by the Scotch-Irish and Germans, none of whom had English accents.
I do hear "gotten" said occasionally in my part of the US, but it's not common. It's a bit like "ain't" in that way.
Likewise, spellings like "programme" are deliberate changes to mimic the French spelling. These have been rather more successful than they have any right to be, but some have completely failed (like "gramme") and a lot of people still use the older spelling.
-ize, also, used to be the standard spelling with -ise an alternative also found in the UK. In this case, it's clear that an understanding that -ize is used in the US and -ise is used in the UK became an understanding that -ize is the US spelling and -ise is the UK spelling which raised its currency. But I think they both remain in use in the UK (-ise has more-or-less chased out -ize in Australia though).
-or spellings like "honor" and "color" were once much more common in places where they are now rarely seen and vice versa. To an extent they follow the same story as -ize/-ise, with the US standardisation of one chasing its use out in the UK. In Australia, -or was much more common (than now) when the power to distinguish oneself from was the UK, but now that the main power one needs to distinguish oneself from is the US, -our has chased it out except in the name of the Labor party (because the paperwork was filed by someone who happened to prefer the shorter spelling in a time when both were current) and some uses of "honor" that are literally etched in stone. (The last general use was until about the year 2000, by "The Age", a Melbourne newspaper which used -or as its house style, but by then it was seen to be improperly American and they switched to -our.)
Generally, spellings and spelling variations remain open and subject to gradual change in all English-writing countries.
The more accurate translation would have be "precious/treasure" -- i.e., Shop for [Treasure]. (Taobao lit. means to [Pan] for [Treasure])
In common colloquial usage, though, the term would indeed refer to "baby" in the same sense as "my precious/darling".
Another very ironic example of that is this recent Reddit post [1], where the name "Nasser" was censored in-game to become "N***er", making it look much, much worse.
[1] https://www.reddit.com/r/gaming/comments/znfw7y/my_name_is_n...
It also brings to mind a translation issue from my home country, wales, where road signs must be bilingual (english and welsh). A request was sent to a welsh translation service asking for the translation for a specific phrase. The signwriters received the response, completed the sign and it was then erected. The problem: it was an out-of-office auto-reply! https://www.snopes.com/fact-check/mistranslated-welsh-traffi...
Either the translators made a mistake, and thought it was referring to a ZIP (regardless of capitalization) and translated accordingly, or a developer used the wrong key when assembling the string references - i.e. he used the equivalent of (this is pseudocode as I dont know how they handle localizations):
localize("CompressToArchive", localize("Zip"), localize("File")) - i.e. with a reference to localization of "Zip" (or ZIP, or zip - the dev likely just searched for a string that matched what he wanted to localize)
instead of localize("CompressToArchive", "Zip", localize("File")) - i.e. with a string of "Zip"
where the strings are defined as: CompressToArchive: Compress to %1.%2 (same for us and uk)
Zip: ZIP (us) or postcode (uk)
File: File (same for us and uk)But you're supposed to find it in QA after that.
In the context of electronics "pin" (as in on a component) translates to French as "broche" but it makes no sense for a pincode!
In India pincode refers to zipcode or postalcode. the pin in pincode means Postal Index Number.
It would be interesting to know if similar bug exists for the locale en_IN.
The Swedish translation said "The touchscreen that starts!"
I can’t imagine a way to make it any more efficient, without sacrificing significant accuracy by missing context, than to do manual translation of everything.
I can’t imagine if, every time I added a button to a UI, an entire team of localization translators mobilizing to make sure the right context came through in every language the UI supported. Not to mention the tools that support that workflow of passing context to translators, compiling the translations, and binding them all into a data structure I can use to populate my UI.
And that’s just for language. Iconography and colors have their own localizations.
A screenshot of just the dropdown menu could have been generated in CI and could have easily prevented the “postcode file”, so long the translator was presented that image along the string and had recognized that Windows dropdown.
You can add context this way, but programmers often forget, translators don't look for context, and seemingly no one reviews the final product in other languages.
The proper solution again, is using keys that provide the context. A special syntax for these neutral strings (e.g. prefix, uppercase, whatever) will quickly show where a translation is missing. Translating is then a mapping from keys to english, or keys to french and so on and never english -> french, even with gettext. Instead of "Zip file" you'd have to hard code ":filetype_zip".
Then, I started playing World of Warcraft and realized how bad the localization is. I mean, the translation isn't bad per se, I really appreciate that they tried to adapt the game to my country's culture and that is totally awesome.
But seeing Blizzard pay a ton of money for some people that don't even play the game to verify if their translation is correct or makes sense is just astonishing to me. When Blizz released the new UI for WoW, there was an option called "snap" which meant "snap to grid". The amazing translator team, having no context and not even the decency of checking the context in game, translated this option as "estalo", which, in portuguese, means "snap (sound)", as in a finger snap.
Another example is that when they added minimap sizing to the UI editor, there's an option that allows the name of the zone to be below the minimap. The brilliant translator team translated it in portuguese to "abaixo cabeçalho" (literally under header) or something very silly which you could literally see that they put no effort in the translation.
Microsoft, at the time: "This is an issue in the latest Canary Channel build and the loc folks are working on a fix" (https://twitter.com/JenMsft/status/1643599284120723456)
Which seems to still be mostly the norm for apps in any desktop OS for things like preferences/settings dialogs.
If the session language is non-US, the ISO formatted string '1991-02-03' becomes 2rd March rather than 3rd Feb. yyyyMMdd works as expected.
Every Photoshop user knows the difference between the image and the canvas, between layers and channels and levels. They learn what dodge and burn mean.
But nobody can even guess what arbitrary terms a translator will use for layers and canvases and channels and levels, or what terms printers used for dodging and burning back in the day.
Not to mention most Photoshop tutorials you find are in English as well.
Professional? Maybe. Elegant? Not the least bit.
MS was the first mover here by having a robust translation of Windows 95 from the start (and yeah, they did translate the start button).
My favorite example of that was a sign at an airport. Marking a spot off for taxis and rideshares. The latter was spelled out phonetically in Cyrillic. I was a little surprised they didn't use the Russian words for "ride" and "share".
You may end up having multiple conflicting ways to describe the same thing or even a person. A few days ago I saw Hades transliterated as Гадеc in some web comic translation, even though he is usually called Аид for many centuries already.
(Though I personally find most Polish translations of software abysmal, especially the translations into Microsoft Polish, and use US/UK English everywhere.)
I remember in Windows 95 (that's been a while) a little binary, probably ipconfig.exe was broken in the Finnish version we had on our home computer. I copied the binary from the English version we had at work and it worked.
Please, for internalisation sake, use the generic term ‘postal code’ in English , then regionalise as appropriate (e.g. Post Code in the UK, Eircode in Ireland, Postal Index Number in India, Zip code in the US, etc.)
That's basically it.
https://twitter.com/Dexerto/status/1605337499873660928?lang=...
On the two Windows 11 machines that I have access to, one Pro and one Home, and both set to UK English, the file compression option says "Compress to Zip file". I've never seen "postcode file" in the Windows UI.
https://www.reddit.com/r/CasualUK/comments/12cwylk/microsoft...
It's odd that apparently nobody on HN bothered to personally check this story, except you. (Is a lesson somewhere for the coming wave of AI fake news?)
Don't need to translate/localize anything when there's no text to translate/localize. Presumably that's easier.
Surely they could have avoided the embarrassment of pushing this to prod?
And I love how the English called filets fill-its but when it comes to eggplants it's aubergine!
What a colourful language.
An LLM first translates to tokens in more of a "concept space", then translates to other languages. So it would translate "zip file" to something completely different than "zip code", and translate to UK English correctly, or at least better I would hope.
They may not solve all problems, but maybe this one?
One is a programmer using the wrong string ID. Probably a mistake when searching a translation file/db.
The second is missing context. The word "zip" has multiple meanings in software, so you need more information to disambiguate when translating. "Zip code" and "zip file" is probably sufficient, but you could imagine them also having a templated translation for file types like "{} file".
I could see an unspecialized LLM translation working well for whole sentences or paragraphs, because that kind of text isn't really likely to run into either of these problems. And if you have the context you need to avoid the second problem for small snippets, then human translation is also pretty unlikely to fail.
Without context, a “zip” or “zip file” still can be anything. Could even be “zip [this] file” as a command.
Most of the concepts in an OS are named by Americans.
If I were using a UK-made OS, I'd happily live with "dustbin" rather than a "trash can". Unless you have your head inserted in your ass, you know some UK words if you're North American and vice versa.
Honestly, speaking as a foreigner, who has been learning English one way or another for half of his life, I cannot even attempt to speak in British accent without feeling like I'm doing a stand-up comedy. How can Brits speak with a straight face?
(from Twitter)