cldr VS VTerminalPaletteEditor

Creating this mapping is a manual process, and the link contains the reference for the mappings. To establish this mapping, you can find the necessary information by visiting the link.

One problem I stumbled upon frequently is codebases that did not support localized formats, but just assumed a certain format to use, for example through concatenation.

There are capabilities built into the programming languages, which allow to format numbers, currencies, etc. with a specific locale. There are also great resources [1] out there that provide all kinds of formats and localized names for countries, currencies, etc.

[1] Unicode CLDR: https://github.com/unicode-org/cldr

Small addition: If you need the characters in machine-readable form, the source is the CLDR project. For Portuguese, the XML file is here on Github: https://github.com/unicode-org/cldr/blob/master/common/main/pt.xml

This information is false. en-150 in CLDR does not use this Euro English variant. It's just world English (en-001) with 3 adjustments: 24 hour time, currency symbol after the number and European time zone codes. Source. That's it.

Going forward, I'd like to focus on writing a tutorial to explain how palettes work and how to create them using the VTerminal Palette Editor. My next goals after that are to continue preparing material for the tutorial series, increasing test coverage, possibly creating a logo for the project, and to continue writing additional guides as necessary.

If you're not used to reflection, the code is going to seem a bit mind-bending at first, but it works quite well. I'm still experimenting with it as well, but I was able to write a working program with it.