You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 17, 2022. It is now read-only.
I'm still in the process of reviewing your translations (I'm Dutch). Though generally I think you are [WikiPedia:Literal_translation translating too literally] and sometimes a bit too much fixed on wanting a Dutch equivalent where there is none.
As an example of the latter case, when translating "All hovers upgraded automatically" you use "luchtkussens" as a translation for "hovers". While that is, technically, a reasonably accurate description of "hovercraft technology", "luchtkussens" is a much too generic word to be reasonably understandable while "hovercraft" is generally quite well understood in Dutch (even though it doesn't originate from Dutch). Instead I suggest that you use something like "Alle hovercrafts zijn automatisch verbeterd." in this case.
I also encountered this:
#: src/clparse.c:98
msgid "Enable a campaign only mod"
msgstr ""
msgstr "Een mod alleen voor veldtocht aanzetten"
#: src/clparse.c:99
msgid "Enable a multiplay only mod"
msgstr ""
msgstr "Een mod alleen voor meerdere spelers aanzetten"
Those ^^ command line options don't have the effect of enabling a mod only for campaign or only for multiplayer (+skirmish actually). Instead we have three categories of mods, those that apply only to campaign, those that apply only to multiplayer/skirmish and those that apply to both. You can in fact have different mods with the same name in different categories. Thus these options all select from those different categories instead of only enabling a mod in the particular cases of campaign/multiplay.
Aside from those few things your translations seem quite good to me. I know this message is quite lengthy, that's not because I consider your translations to be very bad or poor, it's just because I tend to (or attempt to) be very accurate.
Call me a linguistic purist, but I think the amount of English should be kept at a minimum. Using too much English would defy the purpose of a Dutch translation. On the other hand, we don't want the translations to become cheesy or cringeworthy ("tenenkrommend"). Unfortunately, most of the translation work was done late at night, not the most creative time of day. Could you keep a list of all the words that were not ideally translated, so we can try and see what we can come up with?
As for the word hovercraft, what about zweefboot/zweeftuig/kussentuig (by analogy with vliegtuig)?
Final issue: according to the Green Booklet composite nouns should be spelled as one word, i.e. no spaces in between the different components. This is fine for the short words, but for the long ones it becomes rather impractical. I added some hyphens to improve the legibility. For the tank names, I can't think of any solution, except to split them up and use prepositions, e.g. Viper Heavy Machinegun Wheels could become Adder op wielen met zwaar machinegeweer.
Call me a linguistic purist, but I think the amount of English should be kept at a minimum. Using too much English would defy the purpose of a Dutch translation. On the other hand, we don't want the translations to become cheesy or cringeworthy ("tenenkrommend").
Having cringe worthy translations is not as bad as having translations that are difficult to understand IMO. A translation's primary purpose should be to enable people that only understand Dutch to understand Warzone anyway.
Unfortunately, most of the translation work was done late at night, not the most creative time of day.
I beg to differ, it tends to be my most creative time of the day ;-).
Could you keep a list of all the words that were not ideally translated, so we can try and see what we can come up with?
I'll add a list like that as a comment to the translation file.
As for the word hovercraft, what about zweefboot/zweeftuig/kussentuig (by analogy with vliegtuig)?
Ask your (grand)mother, etc. what she would understand by any of the above. If it isn't hovercraft then it's a bad translation. Furthermore I can find "hovercraft" in my 19th print "Kramers" Dutch dictionary (1987):
ho'vercraft m [hovverkraaft] (-s) 1 vaartuig op luchtkussens, dat zich ook boven het water kan bewegen; 2 soortgelijk uitgerust voertuig, dat ook boven de grond zich kan voortbewegen.
Same for my much more recent copy of "Van Dale", but I don't take them
very serious any more since they seem to be including a half-translated
English dictionary and calling it Dutch. I.e. I consider "Van Dale"'s publishers to be more of a bunch of hypesters lately
Final issue: according to the Green Booklet composite nouns should be spelled as one word, i.e. no spaces in between the different components. This is fine for the short words, but for the long ones it becomes rather impractical. I added some hyphens to improve the legibility. For the tank names, I can't think of any solution, except to split them up and use prepositions, e.g. Viper Heavy Machinegun Wheels could become Adder op wielen met zwaar machinegeweer.
A large amount of the tank names are in fact automatically generated in this form " ". So I think it might be best to keep the non-sentence form, and just stick with the "summary" form instead. (The current form is more a summary of components really).
Either way, I'll commit your changes to trunk unchanged and have a look at further translation updates/fixes later on.
As for the word hovercraft, what about zweefboot/zweeftuig/kussentuig (by analogy with vliegtuig)?
Ask your (grand)mother, etc. what she would understand by any of the above. If it isn't hovercraft then it's a bad translation. Furthermore I can find "hovercraft" in my 19th print "Kramers" Dutch dictionary (1987):
ho'vercraft m [hovverkraaft] (-s) 1 vaartuig op luchtkussens, dat zich ook boven het water kan bewegen; 2 soortgelijk uitgerust voertuig, dat ook boven de grond zich kan voortbewegen.
Same for my much more recent copy of "Van Dale", but I don't take them
very serious any more since they seem to be including a half-translated
English dictionary and calling it Dutch. I.e. I consider "Van Dale"'s publishers to be more of a bunch of hypesters lately
I just had a look in the "Groene boekje" (1997 edition). It lists "hovercraft" as being an official Dutch word.
(In [6547]) Merged revision [6546] into the [milestone:2.1] branch via svnmerge from trunk
NOTE: Used a combination of msgcat and msgmerge for merging, not svn's builtin merge, as it doesn't play nice with gettext translation catalogs at all.
Activity
wzdev-ci commentedon Jan 4, 2009
vanRillandBath uploaded file
nl.po
(357.7 KiB)Dutch translation
wzdev-ci commentedon Jan 5, 2009
Giel changed status from
new
toaccepted
wzdev-ci commentedon Jan 5, 2009
Giel changed owner from `` to
Giel
wzdev-ci commentedon Jan 5, 2009
Giel commented
I'm still in the process of reviewing your translations (I'm Dutch). Though generally I think you are [WikiPedia:Literal_translation translating too literally] and sometimes a bit too much fixed on wanting a Dutch equivalent where there is none.
As an example of the latter case, when translating "All hovers upgraded automatically" you use "luchtkussens" as a translation for "hovers". While that is, technically, a reasonably accurate description of "hovercraft technology", "luchtkussens" is a much too generic word to be reasonably understandable while "hovercraft" is generally quite well understood in Dutch (even though it doesn't originate from Dutch). Instead I suggest that you use something like "Alle hovercrafts zijn automatisch verbeterd." in this case.
I also encountered this:
Those ^^ command line options don't have the effect of enabling a mod only for campaign or only for multiplayer (+skirmish actually). Instead we have three categories of mods, those that apply only to campaign, those that apply only to multiplayer/skirmish and those that apply to both. You can in fact have different mods with the same name in different categories. Thus these options all select from those different categories instead of only enabling a mod in the particular cases of campaign/multiplay.
Aside from those few things your translations seem quite good to me. I know this message is quite lengthy, that's not because I consider your translations to be very bad or poor, it's just because I tend to (or attempt to) be very accurate.
wzdev-ci commentedon Jan 6, 2009
vanRillandBath commented
Hi Giel,
Call me a linguistic purist, but I think the amount of English should be kept at a minimum. Using too much English would defy the purpose of a Dutch translation. On the other hand, we don't want the translations to become cheesy or cringeworthy ("tenenkrommend"). Unfortunately, most of the translation work was done late at night, not the most creative time of day. Could you keep a list of all the words that were not ideally translated, so we can try and see what we can come up with?
As for the word hovercraft, what about zweefboot/zweeftuig/kussentuig (by analogy with vliegtuig)?
Final issue: according to the Green Booklet composite nouns should be spelled as one word, i.e. no spaces in between the different components. This is fine for the short words, but for the long ones it becomes rather impractical. I added some hyphens to improve the legibility. For the tank names, I can't think of any solution, except to split them up and use prepositions, e.g. Viper Heavy Machinegun Wheels could become Adder op wielen met zwaar machinegeweer.
wzdev-ci commentedon Jan 11, 2009
Giel changed milestone from `` to
2.2
wzdev-ci commentedon Jan 11, 2009
Giel commented
Replying to Warzone2100/old-trac-import#200 (comment:3):
Having cringe worthy translations is not as bad as having translations that are difficult to understand IMO. A translation's primary purpose should be to enable people that only understand Dutch to understand Warzone anyway.
I beg to differ, it tends to be my most creative time of the day ;-).
I'll add a list like that as a comment to the translation file.
Ask your (grand)mother, etc. what she would understand by any of the above. If it isn't hovercraft then it's a bad translation. Furthermore I can find "hovercraft" in my 19th print "Kramers" Dutch dictionary (1987):
Same for my much more recent copy of "Van Dale", but I don't take them
very serious any more since they seem to be including a half-translated
English dictionary and calling it Dutch. I.e. I consider "Van Dale"'s publishers to be more of a bunch of hypesters lately
A large amount of the tank names are in fact automatically generated in this form " ". So I think it might be best to keep the non-sentence form, and just stick with the "summary" form instead. (The current form is more a summary of components really).
Either way, I'll commit your changes to trunk unchanged and have a look at further translation updates/fixes later on.
wzdev-ci commentedon Jan 11, 2009
Giel commented
Replying to Warzone2100/old-trac-import#200 (comment:4):
I just had a look in the "Groene boekje" (1997 edition). It lists "hovercraft" as being an official Dutch word.
wzdev-ci commentedon Jan 11, 2009
Giel changed status from
accepted
toclosed
wzdev-ci commentedon Jan 11, 2009
Giel changed resolution from `` to
fixed
wzdev-ci commentedon Jan 11, 2009
Giel commented
(In [6546]) Update Dutch translation:
This closes #200, patch by Mathijs
wzdev-ci commentedon Jan 11, 2009
Giel commented
(In [6547]) Merged revision [6546] into the [milestone:2.1] branch via svnmerge from trunk
NOTE: Used a combination of msgcat and msgmerge for merging, not svn's builtin merge, as it doesn't play nice with gettext translation catalogs at all.
........
[6546] | muggenhor | 2009-01-11 22:11:54 +0100 (zo, 11 jan 2009) | 4 lines
Update Dutch translation:
This closes #200, patch by Mathijs
........
wzdev-ci commentedon Feb 16, 2009
DevUrandom changed component from
other
toData: Translation
wzdev-ci commentedon May 8, 2010
Buginator removed milestone (was
2.2
)1 remaining item