The place to talk about Transport Tycoon
https://www.tt-forums.net/
If those don't work the debug window should show some error/warning about them. What do they say? Start with the parameters "-d 3" for example.ickoonite wrote:If you're referring to the bit about small_font, medium_font and large_font, I have tried that (of course), specifying both font paths and simple font names, all to no avail.glx wrote:Take a look in the readme
I've now tried starting it with -d 3, with each of the font lines specified as "/msgothic.ttc" (I put them in the root to avoid issues over paths with spaces in), but there is not a single mention of fonts or anything in the startup debug messages (all the way to the main menu screen), so unfortunately nothing useful I can cut and paste into here for you. (I tried -d 5 too)Darkvater wrote:If those don't work the debug window should show some error/warning about them. What do they say? Start with the parameters "-d 3" for example.ickoonite wrote:If you're referring to the bit about small_font, medium_font and large_font, I have tried that (of course), specifying both font paths and simple font names, all to no avail.glx wrote:Take a look in the readme
I've just rolled another version from SVN (revision 8288), compiling in Freetype (version 2.1.9, for what it's worth - the newest version Fink has), and it's working! I will do a little experimentation with different fonts and report back (because it's not much use if it depends on MS Mincho and MS Gothic, fonts which Mac users may not have).ickoonite wrote:I presume the Mac builds are built against Freetype, although I rolled one myself (admittedly without fontconfig) and it still wouldn't work, so it can't be that it's simply lacking Freetype.
But the problem here is not the font I am using - it is quite clear that no external font is being loaded at all, as I can see that it is still just using the standard bitmap font.
If I can do anything else debug-wise, let me know. I'd be particularly interested to know if anyone can get fonts to work on the Mac build.
Having now had a fiddle round, specifying /System/Library/Fonts/Hiragino Marugo Pro W4.otf, although the filename is Japanese so must be specified as such) works quite nicely, and is a font that will be available on any Japanese Mac user's system.ickoonite wrote:I will do a little experimentation with different fonts and report back (because it's not much use if it depends on MS Mincho and MS Gothic, fonts which Mac users may not have).
Dear Exi,Ezi wrote:I reply to announce that I completed KOREAN TRANSLATION for OpenTTD 0.5.0-RC4.
It works. I just addedickoonite wrote:I'm the Japanese translator for OpenTTD and am a little bit peeved at the moment as the shiny new Unicode, etc. support doesn't appear to work on OS X. I've tried compiling with libfreetype, etc. but to no avail. Bit disappointing really, as it means I am having to run OTTD under Windows on Virtual PC to test out my modifications.
So, yeah, a fix for that would be absolutely brilliant. As it is now, on my system (where the system language is set to Japanese), if you load OTTD up without an openttd.cfg, it defaults to Japanese and thus just a load of question marks, because the font support appears not to be there.
Code: Select all
small_font = /Library/Fonts/Chalkboard.ttf
medium_font = /Library/Fonts/Chalkboard.ttf
large_font = /Library/Fonts/Chalkboard.ttfCode: Select all
/Library/Fonts/Code: Select all
/Users/(your user name)/Library/Fonts/
I just checked out RC4 as requested, built it and it doesn't work. The one caveat to that is that I am not very familiar with the weird (read: differentDarkvater wrote:ickoonite: please check out svn://svn.openttd.org/tags/0.5.0-RC4 because r8288 (HEAD) will not get you 0.5 once it's out.
) configure script - I got a couple of errors running configure, but it built anyway.Code: Select all
./configure --freetype-config=/usr/local/bin/freetype-config --with-cocoa --with-iconv=/usr/include
/bin/sh: --: invalid option
Usage: /bin/sh [GNU long option] [option] ...
/bin/sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--rcfile
--restricted
--verbose
--version
--wordexp
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
touch Makefile.config
touch Makefile.config
make[1]: `Makefile.config' is up to date.
Alas, no it doesn't.Bjarni wrote:It works.
I have already posted about this further up in the thread - /System/Library/Fonts/Hiragino Marugo Pro W4.otf works well. The filename of the font itself is in fact in Japanese, but I cannot post that to phpBB as it doesn't appear to do Unicode, hence my transliteration here.Bjarni wrote:I have no idea on what font to recommend for Japanese though, but trial and error seems to be a decent place to start.
First of all, try to get it working with English. If you add this font, you should get problems with Japanese as it lacks the Japanese letters as well.ickoonite wrote:Alas, no it doesn't.Bjarni wrote:It works.
Just to make sure it isn't me going insane, I have just downloaded a fresh copy of RC4 onto another Mac, which has never had OpenTTD installed on it before, copied only the data files over, loaded it up once (to generate the openttd.cfg file), closed it down, added the _font lines in, specifying exactly the same font as you (checking first to see that it exists on my system), and it still doesn't work.
I have already posted about this further up in the thread - /System/Library/Fonts/Hiragino Marugo Pro W4.otf works well. The filename of the font itself is in fact in Japanese, but I cannot post that to phpBB as it doesn't appear to do Unicode, hence my transliteration here.Bjarni wrote:I have no idea on what font to recommend for Japanese though, but trial and error seems to be a decent place to start.
It doesn't work with English either - that is why I tried using Chalkboard first. Both machines are PowerPCs (one G3, one G4) running 10.4.8.Bjarni wrote:First of all, try to get it working with English. If you add this font, you should get problems with Japanese as it lacks the Japanese letters as well.
If it fails to work with English as well, then we got an issue. What OS and what CPU do you use?
ok, we got a problem here... it works for me, but when I moved the file to another computer, it failed. Now the question is why....ickoonite wrote:It doesn't work with English either - that is why I tried using Chalkboard first. Both machines are PowerPCs (one G3, one G4) running 10.4.8.Bjarni wrote:First of all, try to get it working with English. If you add this font, you should get problems with Japanese as it lacks the Japanese letters as well.
If it fails to work with English as well, then we got an issue. What OS and what CPU do you use?
)I just used the freetype that comes with OSX. How did you manage to get anohter version? Did you compile it yourself or something?ickoonite wrote:Right, that does work. But compared to the one I built against Freetype 2.3.0, the fonts are a bit ugly (particularly an issue in Japanese, where the small font sizes are already making legibility an issue)