Hi. Ranran made a new patch.(´・ω・｀)
I believe this is a long-cherished ambition of the East Asian people. Please give them relief! ;)
Here is my Github branch (https://github.com/Ranran-the-JuicyPork/simutrans-extended/tree/year-month-dispaly-improvements).
This patch is only an improvement of display, and there should be no change in game play.
When playing in English, there should be no change.
In this patch, change the date and time notation in Japanese as follows.
Before:
(https://i.imgur.com/lBTWEum.png)
(https://i.imgur.com/eBK3u1l.png)
This notation was strange in Japanese.
After:
(https://i.imgur.com/e8jWExg.png)
(https://i.imgur.com/kHwtNOn.png)
Yes, this has recently been implemented in standard.
Change from the standard is, it covers the depot window and construction date, and changes the order of year and month according to show_month setting in
simuconf.tab.
The year and the month order is opposite to Western countries even on the depot window.
If show_month=2,5 and
9:
(https://i.imgur.com/W8X8jCz.png)
other, same as currently:
(https://i.imgur.com/kHwtNOn.png)
I extended simuconf.tab option
show_month = 9 .
It is the journey time equivalent indication of the bottom bar same as "show_month=9" but displays the year / month notation in YYYY/MM on the dialog (depot etc) .
I am incorporating and imitating standard's code for this patch and some variables have been changed from German to English according to the current standard's code.
Will these changes interfere with ACarlotti's work?
Converted words are:
karte_ansicht_t | → | main_view_t |
stunden | → | hours |
Three translation texts are added by this patch.
It is for year/month/day symbol - (年/月/日).
It is same as Standard and
recommended not to set anything except translated Japanese/Chinese(YYYY年MM月 style).
I attach .dat file for Simutranlator.
Quote from: Ranran on September 25, 2018, 12:48:19 PM
Will these changes interfere with ACarlotti's work?
At a glance it seems that it probably won't make things harder, although I cannot be sure about this without investigating in far more detail than is worth doing. I think the main source of problems caused by out-of-order porting are when two changes affect the same code, and the second one has been ported first. In those cases I have to look at the version history of that code snippet to work out the history, and thus what or how much needs to be ported (except for the case of translations, where it is often fairly easy to recognise the translation as a separate change even if it's been reordered).
Excellent - thank you for that: now incorporated (including Simutranslator changes).
Thank you for the incorporating. :)
show_month = 9 will be displayed like this even in English.
(https://i.imgur.com/LR1SeY4.png)
In some countries it will be useful, I think. ;)
Quote from: ACarlotti on September 25, 2018, 10:05:44 PMAt a glance it seems that it probably won't make things harder
@ACarlotti - Thank you for your reply.
I hope it will not be difficult.