![]() Translations are isolated locale-specific logic doesn’t leak to other locales. The translation file has a formula to indicate what kind of plurals there are, like this: "Plural-Forms: nplurals=3 plural=n%10=1 & n%100!=11 ? 0 : n%10>=2 & n"īut there are newer systems (supposedly) building on top of lessons learned from gettext, like Fluent, also see here. ngettext("1 item", "%1 items", num_items) This is definitely relevant to at least some strings, like ^You need to turn in %d more photos before returning to your game developer job at MMucasFlem. The basic principle is you pass it an English singular and plural and it takes care of the rest. See here for my own brief summary of what how you’d deal with some of this kind of stuff in gettext. Even if they aren’t applicable to games they could help in implementing such a system in your engine. Maybe you could/should have a look at other Open Source systems that are used to translate software. ![]() However, I am not really sure Ron would be interested in coding such system… Of course, then it would be necessary to add a numeric parameter to each verb.ĭas Messer|des Messers|dem Messer|das MesserĪ face|uma faca|? (sorry, I’m not an expert =) ![]() Sometimes I can cheat a little bit (“Talk to” needs 7th, so I can use “Address” that uses 4th), but unfortunately I need the 3rd for “Walk to” and “Give something to”, the 2nd for “Look into”, etc. For Delores engine I could almost get away with just one (4th = accusative) that works with common verbs (Look at, Use, Push, Pull, etc.) In Czech we have seven possible declensions ( ) of each noun. That would work even for declension in Slavic languages that I can’t properly handle now. I suppose it would be more versatile to create an “array” of possible variations of each item (in your case at least two) and to keep them together. So when you take a pic of a knife, the game takes “knife”, sees if there’s an article, and if not, adds “a”. Meanwhile, this brazilian portuguese translation is as good as it gets (for the first try before many, many corrections and contributions, that is).Īrticles are added on the fly when you take a picture of something. But I don’t know if this is the best approach. Unfortunately, we cant expect to translate “the” or “a” by themselves, without knowing about what they are referring (or can refer), and think that they will work properly with languages with grammatical genders.Ī possible solution is to add an extra tab (extra column) in the tsv files that specifies the gender of an object, char or noun so that we could add an IF in the code that would add the proper pronoun or article before the noun. So I think you can see the problem already. The same can be said with “a fork” and “a knife”: it would be “um garfo” and “uma faca”. Yes, all knifes are females in Brazil and they WILL cut you if you don’t call them by the proper pronoun. Simple example: in english you would say “the fork” and “the knife”, using the same pronoun to both, but in portuguese it would be “o garfo” (‘o’ because fork/garfo is a masculine noun) and “a faca” (‘a’ because knife/faca is a feminine noun). English is gender neutral, but languages like portuguese, french and german are not: the nouns can be masculine or feminine and the pronouns and articles (and sometimes verbs, numerals, adjectives, etc) must form an agreement with the gender of the noun. ![]() Could I change to that without loading errors?Ī serious problem that I found is with grammatical gender ( ). The correct naming would be “pt-br” (portuguese from brazil), I think. I tried to follow the 2 letters rule for naming the file, but it’s not ideal since pt (portuguese) is for portuguese from Portugal which is almostttttt the same, but not quite (similar enough so that we can understand everything, but it will sound weird sometimes).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |