Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
The biggest challenge I've had when writing multilingual user interfaces aren't lacking a way to translate, but just practical issues like dynamic string construction or where the structure of the UI somehow doesn't work in another language, or when a given string is used in multiple parts of the app in the English version, but the non-English versions need different strings in different places[0], or just where an English single word translates into a whole sentence (or vice versa).
[0] For example some languages don't have a commonly used word that means "limb" - i.e. arm _or_ leg. A bit niche, but if you're doing something medical-related it can cause issues.
Technically it is correct, but in doing that you lose the essence of the word “roman” and of the whole influence French culture had over the whole of Europe until not that long ago, including in Germany. It is in these cases where it is quite obvious that Britain was an island at the edge of Europe, culturally and not only.
This seems like a slightly strange objection to me; I would have thought the actual semantic problem lies with "Bildung", in that a Bildungsroman generally involves some kind of learning/development/improvement, whereas a coming-of-age novel does not necessarily involve this.
> It is in these cases where it is quite obvious that Britain was an island at the edge of Europe, culturally and not only.
I mean this is a very weird claim, which assumes that Europe is culturally homogenous (e.g. I think you will find that Britain and France are culturally closer than France and Slovenia).
This isn't specific to concepts like "Bildungsroman." You're essentially saying "this word isn't just a word, but a word with implicit cultural context."
That's true of pretty much every word. Hell, translating "ao" from Japanese, you'd think is so simple: blue. Except it can also mean green because in Japanese there is less historical, cultural distinction between blue and green. So obviously green traffic lights are called "blue" in Japanese, not green.
You'll never get a perfect translation of anything that's longer than a couple words. The point of translation is getting close enough. Translating Bildungsroman as "coming of age novel" gets you so close, that if your conversation hinges on the actual nuance, you're almost assuredly talking to someone who will understand what Bildungsroman means, so you just use that word.
EDIT: One of my friends at uni did his thesis on the difference between Japanese "natsukashii" and English "nostalgic." I've always thought about that as the perfect example of how any simple translation is fraught with cultural complications. There are certainly things I would call "nostalgic" but I'd never call "natsukashii," because nostalgia can come with sadness, but natsukashii never does.
Not sure about Slovenia but there's a lot more France here in Romania (from where I'm from) compared to the France that is present in Britain, that is if we ignore the 1200-1300s Norman direct influences. But that's a different discussion, related to how the insular Brits cannot really comprehend Napoleon's work to the fullest (as a reminder, what is now Slovenia was indeed, if even for a short period of time, under Napoleonic France, with Ljubljana being indeed the capital of what was then a French autonomous province [1])
Yeah I don't get this either. The English culture and language both have clear influences from French, courtesy of the Norman invasion (and other influence points over time of course). It's weird to point to Britain of all places as not being influenced by French culture.