Norwegian Translation
Thrillseeker
Join Date: 2007-04-10 Member: 60593Members
Join Date: 2007-04-10 Member: 60593Members
<div class="IPBDescription">Norwegian translation of NS2</div>I'm currently doing my best to translate to Norwegian language. I've contributed with something close to 30% of the language so far, and hope more Norwegians at least will contribute voting if not translating also. I see lots of votes missing around the middle. Seems like people start at bottom or top, then scroll down or up, before they give up because there's simply so much to scroll through. This leaves as said an empty hole in the middle of the translation, so please scroll through the whole thing and help vote at least. Thanks!
Comments
-Mikrostorm
kevad95: Here's the translation page. You might need to register there to be able to read and write <a href="http://translate.unknownworlds.com/?module=admin&sm=translation&lid=10" target="_blank">http://translate.unknownworlds.com/?module...tion&lid=10</a>
The problem with not deciding on this early is that we'll have a possible outcome of a very mixed translation, some English words, some Norwegian words, in both tooltips and descriptions. The guidelines say this: <!--quoteo--><div class='quotetop'>QUOTE </div><div class='quotemain'><!--quotec-->You SHOULD NOT TRANSLATE anything vital to the communication of the game, like structure names, alien names, abilities, upgrades, etc. A way to discover if something is translatable or not is asking yourself: "Will people using different translations be able to communicate what's the game status or request something?". For example, if you joined a spanish server and read "Tienen Hive en Data Core, han puesto Shades, tendrán Celerity en cualquier momento", you may not know exactly what is being said, but you can tell what is going on, as "Hive", "Shade" and "Celerity" will be (or should be) the same in all translations.<!--QuoteEnd--></div><!--QuoteEEnd-->
I would say we should follow this when we translate - and we should go over the strings already translated and edit it to reflect this. Also, do we have a community-chosen admin who's actively following the additions in the Norwegian translation?
The guidelines Crabfruit mentioned should be followed, although we should probably expand on that a bit:
Alien lifeform names, such as Skulk, Fade etc., upgrades and abilities, and structure names should be conserved by the guideline example. But what about terms such as Commander, (Kommandør), Armory (Arsenal or Våpenarsenal) and Shotgun (Hagle)?
Once we actually have an overview of what should be translated and what should not, the task should be easier, and likely more focused on making the sentences norwegian in structure rather than norwegian words with an english structure.
=)
I vote for keeping English words on names vital for communication. If we use "Shotgun" instead of "Hagle" then people saying "SG" will understand it's a "Shotgun".
I vote for keeping English words on names vital for communication. If we use "Shotgun" instead of "Hagle" then people saying "SG" will understand it's a "Shotgun".<!--QuoteEnd--></div><!--QuoteEEnd-->
I totaly agree with this, names structures etc should have the same names as in english.
A follow-up question: How should we deal with plurals? "Fades" vs. "Fader", "Skulks" vs. "Skulker"? It doesn't show up that much but it looks a bit cringe-worthy either way. I am leaning towards the norwegian plural suffix "-er" though.
A follow-up question: How should we deal with plurals? "Fades" vs. "Fader", "Skulks" vs. "Skulker"? It doesn't show up that much but it looks a bit cringe-worthy either way. I am leaning towards the norwegian plural suffix "-er" though.<!--QuoteEnd--></div><!--QuoteEEnd-->
Onos is not a verb so I would rather vote for "går Onos" than "Onoser" (which really isn't a word, because Onos ain't a verb). Onos is character name, but having said that, NS1 treat the name also as a verb, when they use words like "Onosing", so I do understand if people want to say "Onoser" but in the end it's not correct. Should be "goes Onos" / "going Onos" in NS1 as well instead of "Onosing" which is so wrong.
That's like saying: "Thrillseeking" if I was to be a character name ... "going Thrillseeker" would be much more correct, even if this is a bad example you get the point.
Sorry if I'm ###### here, but seeing UWE using words like "Onosing" I don't see why we could not use "Onoser". I just personally don't support it, but I can live very well with this solution as well ;)
I agree with you completely on your point regarding "går Onos" vs. "Onoser" as a verb. However, I was actually speaking of plural: Multiples of Onos such as "En onos", "flere Onoser", "alle Onosene" etc.!
For example, let's look at the sentence: "Allows Skulks to self-destruct, damaging nearby enemies". I'd say that this should translate to "Lar Skulker selvdestruere og skade fiender nær seg" or something similar.
Ever tryed translating Dutch into Norwegian? If you do that you can't say it streight forward you have add exstra words etc. to get it correct.
Exsample: "Lar din Skulk selvdestruere og skade fiender nær seg" (or something like that)
What do you guys think?
@kevada95: I also agree that translating word for word from English to Norwegian will make less sense in some situations, than actually rearranging the whole sentence, so it becomes proper Norwegian. I think people should not be afraid rearrange the sentences (even add and remove words) if the end product of that sentence makes more sense / is more understandable in Norwegian.
The swedish translation thread had some good points. I'll just paste my reply to that thread below.
<!--quoteo--><div class='quotetop'>QUOTE </div><div class='quotemain'><!--quotec-->I like the approach of using swedish names in the descriptions only, while keeping english for the titles. We might simply adopt that in the norwegian translation as well.
An idea, unless it bloats too much, might be adding both terms in the descriptions. A tooltip like "Allows welders to be purchased at the armory" could have something like "Tillater kjøp av sveiseaparat (Welder) fra våpenarsenalet (Armory)" and its swedish equivalent.<!--QuoteEnd--></div><!--QuoteEEnd-->
The swedish translation thread had some good points. I'll just paste my reply to that thread below.<!--QuoteEnd--></div><!--QuoteEEnd-->
Brilliant idea to have english names locked in like "(Welder)". I vote for this.
We should have an admin so that we at least can start approving those translations with most votes. Also, so we can start editing:
"Oppgrader til Avansert Arsenal" [ 16p. / good / bad ]
to:
"Oppgrader til Avansert Arsenal (Advanced Armory)" [ 16p. / good / bad ]
If admin gets edit access too this could be done. But of course, first we got to agree if this is the approach we want.
"Harvester under angrep"
"Hive er ferdigbygget"
Men så:
"Redet (Hive) dør"
"Redet (Hive) under angrep"
Furthermore, if we're using parentheses, should we translate every name this way? Should we find alternatives to Skulk, Gorge etc and then put the original in parentheses? After all these names make perfect sense as words in English. What about abilities? Should it be "Adrenalinsporer (Adrenaline Spurs)"? What about "Lerk (Lerk)"? "Skulk (Skulk)? To be honest I think it might get a bit messy doing it this way. We wouldn't want the entire screen filled up by alternatives. It would be great though if we could agree on one approach and only approve translations that follow it. Personally I think we should leave parentheses out altogether like every other translation I looked at has (German, French, Swedish) and simply leave names untranslated.
There are also stylistic issues: Should "Gorge building Harvester" be "Gorge bygger Harvester" or the currently approved "En Gorge bygger en Harvester"? The latter is basically "A Gorge is building a Harvester", which they chose not to write because it (like its direct Norwegian translation) is drawn out and awkward. This is not an isolated example, and in my opinion it would be better to cut some of the "en" and "-en" just like they cut "a" and "the".
I'd also like to see structures translated as "strukturer" across the board, since "bygninger" is simply wrong. Alien structures and most marine structures are no more "bygninger" than "høyspentmaster", "statuer", "murer" and "trafikklys" are.
Another problem I found is how armor is translated differently in different places. "Armor", "beskyttelse", and "rustning" were all approved in different places, and "panser" also seems popular.
Finally, I think "utvikle" is used a bit too much, as it currently translates "spawn", "research" AND "evolve" all at once. The problem is that the alternatives I can think of tend to be a bit awkward.
"Harvester under angrep"
"Hive er ferdigbygget"
Men så:
"Redet (Hive) dør"
"Redet (Hive) under angrep"
Furthermore, if we're using parentheses, should we translate every name this way? Should we find alternatives to Skulk, Gorge etc and then put the original in parentheses? After all these names make perfect sense as words in English. What about abilities? Should it be "Adrenalinsporer (Adrenaline Spurs)"? What about "Lerk (Lerk)"? "Skulk (Skulk)? To be honest I think it might get a bit messy doing it this way. We wouldn't want the entire screen filled up by alternatives. It would be great though if we could agree on one approach and only approve translations that follow it. Personally I think we should leave parentheses out altogether like every other translation I looked at has (German, French, Swedish) and simply leave names untranslated.
There are also stylistic issues: Should "Gorge building Harvester" be "Gorge bygger Harvester" or the currently approved "En Gorge bygger en Harvester"? The latter is basically "A Gorge is building a Harvester", which they chose not to write because it (like its direct Norwegian translation) is drawn out and awkward. This is not an isolated example, and in my opinion it would be better to cut some of the "en" and "-en" just like they cut "a" and "the".
I'd also like to see structures translated as "strukturer" across the board, since "bygninger" is simply wrong. Alien structures and most marine structures are no more "bygninger" than "høyspentmaster", "statuer", "murer" and "trafikklys" are.
Another problem I found is how armor is translated differently in different places. "Armor", "beskyttelse", and "rustning" were all approved in different places, and "panser" also seems popular.
Finally, I think "utvikle" is used a bit too much, as it currently translates "spawn", "research" AND "evolve" all at once. The problem is that the alternatives I can think of tend to be a bit awkward.<!--QuoteEnd--></div><!--QuoteEEnd-->
Great feedback and observations, I must confess I agree on all points. I've been too quick on approving some of the strings (and approving some of my own without allowing for feedback), so I'll backtrack a bit with your thoughts in mind!
Example: Translate "Armor"
- Rustning 22 votes
- Panser 10 votes
- Armor 4 votes
Example: Translate "Your armor is weakened"
- Din armor er svekket. 9 votes
- Ditt panser er svekket. 12 votes
- Din rustning er svekket. 10 votes
This is really realistic, you sometimes see this example. In case #1, we have a clear winner. In case #2, the clear winner in case #1 is not the winner, but still close to the winner of case #1. I think that admins should force the word "rustning" on ALL sentences if this got most votes in the "basic translation (case #1)" even if it doesn't got the most voted in other translations (case #2). I'm bad to explain, hope you guys got me.
1. Lerk, Onos, Gorge, Fade, Skulk, Alien(s), Marine(s), Jetpack, Heavy <b>have not been translated</b>.
2. Attacks, structures etc. <b>have been translated</b>, as far as translation is possible. (the reason I chose to go for translation here is because the community came up with such great alternative names, and to drop these would be such a waste in my opinion)
Vote, vote vote! :D