You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After little research I found that RCG can support more languages than original 10.
List of supported languages can be found in one of structures, and, as I can see, can be easily extended. Main issues is supported fonts and translated entries to specific language.
First issue is not real problem if new language belongs to list of already supported character families:
Latin-1 (maybe even more extended ISO 8859 code pages, such as ISO 8859-15)
Cyrillic
Traditional Chinese
Simplified Chinese
Korean
Japanese
Second issue can be solved with my tool RCG-Tr, which can extend original RCG_LocalizationData.json with new language entries.
So, we can create new localization subproject somewhere in Transifex or Weblate/Pootle server instance to gather translators.
Since RCGModd 1.3 adds new strings (#21), we can use this subproject to translate them too.
The text was updated successfully, but these errors were encountered:
After little research I found that RCG can support more languages than original 10.
List of supported languages can be found in one of structures, and, as I can see, can be easily extended. Main issues is supported fonts and translated entries to specific language.
First issue is not real problem if new language belongs to list of already supported character families:
Second issue can be solved with my tool RCG-Tr, which can extend original
RCG_LocalizationData.json
with new language entries.So, we can create new localization subproject somewhere in Transifex or Weblate/Pootle server instance to gather translators.
Since RCGModd 1.3 adds new strings (#21), we can use this subproject to translate them too.
The text was updated successfully, but these errors were encountered: