We are looking for new/extra translators for the following languages, the number of missing strings as of writing is between parentheses:
Basque (2627)
Esperanto (516)
Frisian (1739)
Galician (145)
Icelandic (119)
Ido (3094)
Japanese (172)
Luxembourgish (124)
Macedonian (2667)
Malay (271)
Persian (1900)
Thai (2388)
Urdu (3023)
Welsh (115)
The FAQ of WT3 tells you how to become a translator. The languages not in this either have less than 100 missing strings, or are totally untranslated. See the translation status for more information about the current status of the translations. Generally speaking not much has happened to this list since 1.0.0-beta3, except the Vietnamese translators translating about 1800 strings.
The deprecation of the Mac OS X port, some user patches were applied but we still do not have an active maintainer of the port and there are still a number of open bug reports.
Finally we would like to ask whether you can help improve the documentation in the wiki so our new players have a good and up-to-date manual to help them exploring OpenTTD.
Not anymore; the script to generate the changelog automatically was broken. Should be fixed now (again), but that's something we'll see with the next release.
If you run the same savegame in beta3 and then load it in beta4 is it slower then in beta4?
If you just had the same game that you started in some version and then moved along with it it will naturally come to a point when things will start to get slower (in non-fast forward mode) because the CPU can't keep up anymore. Many trains, road vehicles, ships and AIs can slow down the game. (and I have possible forgot something else that is also important)
My OpenTTD contributions (AIs, Game Scripts, patches, OpenTTD Auto Updater, and some sprites) Junctioneer (a traffic intersection simulator)
Might be that the bug in the AI API caused AIs to not build proper roads, so they weren't as active/had no money to build stuff and thus OpenTTD seemed faster.
Bilbo wrote:Hmm ... what is the new "Content mirroring support" feature?
A method to prevent the single content server we had to be swamped by content downloads when 1.0.0 is released (by means of load balancing). Given the enormous spikes in traffic for 'only' the beta we expect a big bandwidth spike when the stable is finally released and we would like to 'share' that spike with the mirrors. It also means that generally speaking the downloads can be a bit faster as it's likely that the server is closer to you.
Rubidium wrote:Given the enormous spikes in traffic for 'only' the beta we expect a big bandwidth spike when the stable is finally released and we would like to 'share' that spike with the mirrors. It also means that generally speaking the downloads can be a bit faster as it's likely that the server is closer to you.
I have several 15Mbit lines i happily let you use for serving the ones who want to download it
Just let me know if you would like the extra bandwith
Starbud wrote:I have several 15Mbit lines i happily let you use for serving the ones who want to download it
Just let me know if you would like the extra bandwith
Don't consider this as offer to maintain Ubuntu version. This was my 2nd successful .deb build so it's probably not 100% valid. I also build it without liblzo2-2 meaning old savegames don't work.
