<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to localize an Add on in Archicad C++ API</title>
    <link>https://community.graphisoft.com/t5/Archicad-C-API/How-to-localize-an-Add-on/m-p/225096#M4926</link>
    <description>&lt;BLOCKQUOTE&gt;LesWoolsey wrote:&lt;BR /&gt;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.&lt;/BLOCKQUOTE&gt;
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.</description>
    <pubDate>Mon, 19 Oct 2015 10:53:12 GMT</pubDate>
    <dc:creator>Ralph Wessel</dc:creator>
    <dc:date>2015-10-19T10:53:12Z</dc:date>
    <item>
      <title>How to localize an Add on</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/How-to-localize-an-Add-on/m-p/225095#M4925</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;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.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Les&lt;/DIV&gt;</description>
      <pubDate>Thu, 13 Jul 2023 13:17:39 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/How-to-localize-an-Add-on/m-p/225095#M4925</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-07-13T13:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to localize an Add on</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/How-to-localize-an-Add-on/m-p/225096#M4926</link>
      <description>&lt;BLOCKQUOTE&gt;LesWoolsey wrote:&lt;BR /&gt;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.&lt;/BLOCKQUOTE&gt;
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.</description>
      <pubDate>Mon, 19 Oct 2015 10:53:12 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/How-to-localize-an-Add-on/m-p/225096#M4926</guid>
      <dc:creator>Ralph Wessel</dc:creator>
      <dc:date>2015-10-19T10:53:12Z</dc:date>
    </item>
  </channel>
</rss>

