I congratulated Kit earlier today, now I see it on my wall but not on hers. In fact, there are no walls. Just some random pages scattered around places.
+1 for pointing out the difference between translation and localization. It's not that important in the context of desktop applications, but it is a huge issue on the Web and in print. There is an enormous difference between translating a phrase willy-nilly, translating it really well, and coming up with a set of completely different phrases that are tailored to various nationalities but still convey the same basic idea. — RegDwighтSep 16 '10 at 18:00
@Cerberus Word. This is precisely the problem with A>B translation. You have to know how language B would express a concept in a particular cultural situation.
Example:
— What is he called?
— I have not a clue.
— What is he called?
— I have no clue.
Are both versions grammatical in English? If they are, which one is preferred by native speakers in the US and the UK?
The code base at work has all these "to do" comments. Suggestions for improvement. And lots of them say MCDS after them. I figured it stood for "maybe could do someday". Turns out it's the team leader's initials.
I hate sand cookies, because the name keeps telling me they're made out of sand. And I don't like sand in my cookies. You know, I have this thing about sand in my food.
That would suck to be synesthetic and epileptic, and what the hell, also a lucid dreamer. Pretty much anything could set you off, the smell of fried eggs cooking, a rainbow, dog breath.
Example:
— What is he called?
— I have not a clue.
— What is he called?
— I have no clue.
Are both versions grammatical in English? If they are, which one is preferred by native speakers in the US and the UK?
English Language & Usage: Multi-Layer…
English Language & Usage: Multi-Layer…