My 3 years experience with Perforce was not one of the best ones and I decided to share some things that you may not know about Perforce, ones that you are not going to find in any marketing document.
I’ve always thought it’s hard to find statistical information regarding software localization, so I decided to gather some of them in one place. Here are some data that I collected over time regarding localized text. I hope you may find them useful.
I compiled a small list of things that any developer should know about Unicode.
This article tries to complete a previous article regarding internationalization of keyboard shortcuts. I decided to analyze a few cases, in order to explain better how we should define keyboard shortcuts in a way that will keep them working on most international keyboards.
If you localize only for the macro-language use the macro language code. If you have only one English use just “en” code but if you have more than one “en” will mean “en-US” and you will have to add more detailed codes and like “en-CA”.
On Windows console and Unicode are not quite friends. Here is some code that I use in order to assure that my Python scripts output is consistent on all platforms and is supporting Unicode encoded as UTF-8.
You’ll be able to see the right characters if you are running on Windows 7 but on Windows XP you’ll see the UTF-8 codes displayed as ANSI. Even with this problem you’ll be able to redirect the output of stdout or stderr to files in order to store UTF-8 output.