Modding, Mission Design, and Coding > Test Builds
Unicode text support
Arkblade:
--- Quote from: m!m on December 25, 2017, 03:11:35 am ---The newest nightly now contains a fix to how FSO passes the speech text to the WIndows API which should fix the issue with Japanese text.
--- End quote ---
thank you!
Arkblade:
Have you made progress? The major problem seems like he presented.
--- Quote from: Nikogori on December 13, 2017, 07:46:49 am ---I'd like to report a couple of problems I could find so far. I understand there's a workaround for each of these but it would be great if FS2 Open can handle them.
“Token too long” error is a little too unforgiving. There are only 14 letters in the line but the error message says “Length = 42”. I believe this is UTF-8 related problem... Some Japanese characters (including hiragana, katakana and kanji) take 3 bytes in UTF-8.
--- Code: ---Warning: Training-2.fs2(line 832):
Warning: Token too long: [プライマリウェポンを選択しろ]. Length = 42. Max is 31.
File: parselo.cpp
Line: 301
--- End code ---
I don't know what “MAX_BRIEF_LINE_LEN” means but it seems Japanese briefing text is too long to display (actually they are not that long). Cutting them in half can fix this error.
FS2 automatically starts a new line when it encountered space (the one which appears when you hit “space” key) in Japanese text. Obviously you can avoid this by not using space at all.
--- End quote ---
m!m:
Unfortunately I did not have time to work on resolving this issue.
AdmiralRalwood:
--- Quote from: Nikogori on December 13, 2017, 07:46:49 am ---“Token too long” error is a little too unforgiving. There are only 14 letters in the line but the error message says “Length = 42”. I believe this is UTF-8 related problem... Some Japanese characters (including hiragana, katakana and kanji) take 3 bytes in UTF-8.
--- Code: ---Warning: Training-2.fs2(line 832):
Warning: Token too long: [プライマリウェポンを選択しろ]. Length = 42. Max is 31.
File: parselo.cpp
Line: 301
--- End code ---
--- End quote ---
In this particular instance (assuming line 832 is in the same as in the original mission file, and/or that I've correctly retranslated your too-long token back into English), there's no real reason for objective text to be limited to NAME_LENGTH since they're dynamically allocated anyway (and the final buffer they get put into for display purposes is 256 bytes long). So, in this specific situation, the maximum allowed length could theoretically be increased without really affecting anything else. The one potential problem is that the code doesn't work right for more than two lines of text, but given that we're dealing with text that takes up more bytes without taking up significantly more width, some sort of allowance could probably be made.
--- Quote from: Nikogori on December 13, 2017, 07:46:49 am ---FS2 automatically starts a new line when it encountered space (the one which appears when you hit “space” key) in Japanese text. Obviously you can avoid this by not using space at all.
--- End quote ---
Well, yes, if there's only one space in a long string of text, wordwrapping will generally force a linebreak there. Now, granted, I'm no Japanese expert, but surely you can just... add more spaces, so there are other, more natural places for wordwrapping to break lines? If not, well, can you maybe use a non-breaking space (U+00A0)?
Nikogori:
--- Quote from: Arkblade on January 28, 2018, 12:41:40 pm ---Have you made progress? The major problem seems like he presented.
--- End quote ---
As I said before, these “problems” can be easily avoided. There is workaround for each of them.
“Token too long” error is a bit annoying, though. Sometimes it is very difficult to explain mission objectives in a 10-letter text...
--- Quote from: AdmiralRalwood on January 29, 2018, 12:25:16 pm ---Well, yes, if there's only one space in a long string of text, wordwrapping will generally force a linebreak there. Now, granted, I'm no Japanese expert, but surely you can just... add more spaces, so there are other, more natural places for wordwrapping to break lines? If not, well, can you maybe use a non-breaking space (U+00A0)?
--- End quote ---
I'd like to use existing old Japanese localization patch. Sadly it contains hundreds of “spaces” and it will take some time to remove/replace all of them.
However, if you guys believe it is not easy to let FSO handle them properly, of course I can do this task manually. I guess there are other Japanese players who want to join.
I've been busy working on my own project (I'm writing a blog about Orbiter simulator). I'll be back on this localization project as soon as my current project is finished (Hopefully it will be done by April).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version