How to localize an Add on
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-10-16
06:59 PM
- last edited on
2023-07-13
03:17 PM
by
Doreena Deng
2015-10-16
06:59 PM
Is there any documentation or examples for how to localize an AddOn? I have my English messages etc in a GRC file. The examples sort of lead me to believe that I need a GRC file for each language. But is there a naming convention or is there some way I indicate the language in the GRC file? Do I create a single Add-on or must I create one for each language? It's all very unclear without some sort of guidance. Any suggestions, pointers or examples would help.
Thanks
Les
Thanks
Les
Labels:
- Labels:
-
Add-On (C++)
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-10-19 12:53 PM
2015-10-19
12:53 PM
LesWoolsey wrote:At the moment, the best approach is to make a separate build for every different language (using the relevant GRC files). ARCHICAD and its API don't currently provide a method to bundle all languages in an add-on and switch on demand. You could implement something like that yourself, but I think it's better/simpler to make separate builds.
Is there any documentation or examples for how to localize an AddOn? I have my English messages etc in a GRC file. The examples sort of lead me to believe that I need a GRC file for each language. But is there a naming convention or is there some way I indicate the language in the GRC file? Do I create a single Add-on or must I create one for each language? It's all very unclear without some sort of guidance. Any suggestions, pointers or examples would help.
Ralph Wessel BArch
Central Innovation
Central Innovation