Messages

1

Translations / Re: Japanese version

« on: October 30, 2013, 11:45:14 pm »

Yes that's what I meant with "fix it up", I have to update it to match our language format, then I'll put it up on GetLocalization and people can fill in and correct the missing info.

Fixing up the strings does not sound that hard. I started to recreate the format of the en-US.yml file in the jp-JP.yml file and already found a few errors in the translations (switched translation strings in the Japanese version; my current version where I added some of the missing strings without a corresponding translation is attached).

Would the file be usable in GetLocalization when I continue to add the missing strings from  en-US.yml to jp-JP.yml and remove the ones that are only in the latter?

2

Translations / Re: Japanese version

« on: October 29, 2013, 08:59:54 pm »

Nice!

There seem to be a few missing strings still so we could add those if that has not been done yet by someone else.

1214 en-GB.yml
1214 en-US.yml
1036 jp-JP.yml

3

Programming / Re: yaml-cpp version 0.5 migration?

« on: August 27, 2013, 11:42:51 pm »

Sorry I dropped the ball on this one. I started converting the first 20-30 files but the whole thing took much longer than I expected and I wasn't sure whether I actually converted the sources in the best way possible.

On my machine everything is working fine using yaml-cpp 0.5 now, so that at least is one positive!

4

Programming / yaml-cpp version 0.5 migration?

« on: February 01, 2013, 08:57:07 pm »

The yaml-cpp library version 0.5 was released a few weeks ago and apparently they changed the API quite a lot. It seems like the old API that is currently used in OpenXcom (yaml-cpp version 0.3) will still be supported for the time being though.

I started updating the sources to the new API version but then thought I would first ask here whether a migration is actually planned/wanted. I can offer to try to maintain a github fork adjusted to the new API version  (would make a good git training for me) if you think that would be helpful. What do you think?

5

Translations / Re: Linguistics and style discussion station

« on: November 03, 2011, 07:21:11 pm »

Nice! I will write again if I find something else (maybe on github if it's something larger).

Would it be possible that changes of Text field sizes negatively affect other languages (i. e. their Text positioning) or are we safe in this regard?

6

Translations / Re: Japanese version

« on: November 03, 2011, 07:14:42 pm »

Sounds good to me! I will just set this thread to 'notify me' so that I will be informed about the newest developments on this front.

7

Translations / Re: Japanese version

« on: October 30, 2011, 10:27:31 pm »

Do we have any news on Japanese fonts/translations?

I majored in Japanese Studies so while I am certainly not a native speaker I might be able to support the translation efforts. 

8

Translations / Re: Linguistics and style discussion station

« on: October 30, 2011, 10:18:03 pm »

Funny that there is such a thread because I was just wondering where I should put this:

- The translation string for the German STR_QUIT and STR_CANCEL is the same and in my opinion wrongly so (I am a native speaker). It bugged me every time I exited the game to be honest...

- And I realized that the German Patrolling string loaded in CraftPatrolState.cpp is too long to fit the Text field. I arbitrarily increased the Text field width for this string and checked whether the change affects the English version of the game which does not seem to be the case. I do not know how the other versions will fare though...

(Patch attached for reference)

How do you think such cases should be handled best?