Guidelines for Contributing to QB64
#6
One more thing. Setting "C locales" could suck a lot. I had a music application fail because of it, because I was trying to use a plug-in in which the loaded sound names were in French, with accents and whatnot. I was forced to use a different program that could handle those names and save independent files with names as if they were in English. Another program didn't display stuff correctly due to a font it asked for a language other than English. The cases were rare, though, and this was 32-bit and a long time ago. Now we have Unicode to worry about which could present new headaches only because it has to represent almost every symbol that could be had in writing, especially Asian languages. No wonder a lot of programs cost money that handle elegantly switching from one language to another. The Linux distro builders such as the Russians of ALT Linux have to be praised as well as few other examples of free software.

Almost forgot to mention that I purchased a music plug-in that crashed after I acquired an update... because the developers moved it up to Unicode. Also no configuration would load into the new baby that I had saved with the older version. It was frustrating.
Reply


Messages In This Thread
Guidelines for Contributing to QB64 - by SMcNeill - 05-13-2022, 07:46 PM
RE: Guidelines for Contributing to QB64 - by Fifi - 09-13-2022, 04:47 PM
RE: Guidelines for Contributing to QB64 - by mnrvovrfc - 09-14-2022, 03:50 PM
RE: Guidelines for Contributing to QB64 - by Fifi - 09-14-2022, 05:30 PM
RE: Guidelines for Contributing to QB64 - by Jack - 01-10-2023, 02:48 AM



Users browsing this thread: 15 Guest(s)