I cannot find 'readme' in the game's directory and this topic.Rubidium wrote:Set a font with Simplified Chinese unicode glyphs in openttd.cfg as described in the readme.
OpenTTD 0.5.0-RC5
Moderator: OpenTTD Developers
Also no readme.txt? Anyway http://openttd.org/readme.txtchentz wrote: I cannot find 'readme' in the game's directory and this topic.
Thank you very much!I've found a way to solve this Q.Rubidium wrote:Also no readme.txt? Anyway http://openttd.org/readme.txtchentz wrote: I cannot find 'readme' in the game's directory and this topic.
Here I offer the config lines(You have to copy the font file simsun.ttc):
small_font = simsun.ttc
medium_font = simsun.ttc
large_font = simsun.ttc
small_size = 8
medium_size = 12
large_size = 20
Re: OpenTTD 0.5.0-RC5
I have a MacBook (rev. A), but using two finger scroll on the map only zooms in and out. Should I enable this feature somehow?Darkvater (on '[url=http://www.tt-forums.net/viewtopic.php?p=532327#532327]OpenTTD 0.5.0-RC1[/url]') wrote:
- - Feature: [OSX] Macs with touchpads that support two finger scrolling can now use this feature to move around the map (r5460)
-- Mikko
Japanese translator here seconding the call for configurable (or localisation-based) order of date display. DDMMYYYY makes very little sense in Japanese.thomasau wrote:We are having problems (I believe Jap/SC are having the same problem) on the date translation and the Company League table. First of all, could the date format be re-arranged to YYYYMMDD ? It looks more natural to Chinese and Japanese when the dates are in Chinese characters (kanji).
One question: does Japanese need the reverse order for all date formats in OTTD? So:ickoonite wrote:Japanese translator here seconding the call for configurable (or localisation-based) order of date display. DDMMYYYY makes very little sense in Japanese.
1th Jan 2000 becomes 2000 Jan 1th
January 2000 becomes 2000 January
01-01-2000 becomes 2000-01-01
In a word, yes.Rubidium wrote:One question: does Japanese need the reverse order for all date formats in OTTD? So:
1th Jan 2000 becomes 2000 Jan 1th
January 2000 becomes 2000 January
01-01-2000 becomes 2000-01-01
To my mind, the best way to solve this problem is just to have a localisable string, so that we could do something like:
For short dates:
English: {DAY}/{MONTH}/{YEAR}
Japanese: {2:YEAR}/{1:MONTH}/{0:DAY}
For long dates:
English: {DAY}{TH} {MONTH} {YEAR}
Japanese: {2:YEAR}nen{1:MONTH}gatsu{0:DAY}nichi
(except that instead of nen, gatsu and nichi you have Japanese characters)
The same applies to Chinese as well.
Hope this is useful. Any questions, just ask me.
What I've got now (in english.txt)
Which would translate to the following formatted strings:
DATE_TINY = 31-12-2006
DATE_SHORT = December 2006
DATE_LONG = 31st Dec 2006
The day and month of DATE_TINY are strings as they are zero-padded (those numbers are not in the translation file).
I hope that this is what you wanted. You can try it yourself with the attached diff.
Code: Select all
STR_DATE_TINY :{STRING}-{STRING}-{NUM}
STR_DATE_SHORT :{STRING} {NUM}
STR_DATE_LONG :{STRING} {STRING} {NUM}
DATE_TINY = 31-12-2006
DATE_SHORT = December 2006
DATE_LONG = 31st Dec 2006
The day and month of DATE_TINY are strings as they are zero-padded (those numbers are not in the translation file).
I hope that this is what you wanted. You can try it yourself with the attached diff.
- Attachments
-
- japanese_dates.png (24.26 KiB) Viewed 3147 times
-
- language_configurable_date_format.diff
- Made for trunk r8889
- (11.78 KiB) Downloaded 169 times
Who is online
Users browsing this forum: No registered users and 11 guests