Hmm, I guess we'd have to add, or modify, an action 7 variable. What's more useful, checking individual unicode locations are defined, or just a general "we can use any unicode character" variable?DaleStan wrote:Is there any way I can detect that the OpenTTD in question has UTF-8 support? If so, I'll check for that too, and load the strings if either the GRF or libfreetype is available
Planeset newgrf
Moderator: Graphics Moderators
He's like, some kind of OpenTTD developer.
Well, I expected to be checking var 9D first, but it seems to me that one of the var 85 bits would also work.
As an NFO coder, a bit somewhere that means "don't load these strings if they contain characters whose glyphs aren't available" would be the easiest, but it may not be feasible.
As an NFO coder, a bit somewhere that means "don't load these strings if they contain characters whose glyphs aren't available" would be the easiest, but it may not be feasible.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Who is online
Users browsing this forum: No registered users and 11 guests