<?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: Localizing the ribbon in .NET Forum</title>
    <link>https://forums.autodesk.com/t5/net-forum/localizing-the-ribbon/m-p/2608998#M67759</link>
    <description>Store the localized strings for multiple locales in an Excel worksheet, using the column containing the English language strings as &lt;BR /&gt;
the key column, and additional columns containing the localized strings for each language, one column for each locale.&lt;BR /&gt;
&lt;BR /&gt;
Then write an XML process that takes the English language CUI file (processing it as an XML file) and the Excel Worksheet, and from &lt;BR /&gt;
that, generate localized CUI files.&lt;BR /&gt;
&lt;BR /&gt;
That would be the easiest way to generate and maintain locale-specific CUI files, and would only require you or the translator to &lt;BR /&gt;
enter data into an Excel worksheet, which is far less error prone than manually editing many CUI files or (gasp) using AutoCAD's CUI &lt;BR /&gt;
dialog.&lt;BR /&gt;
&lt;BR /&gt;
Whether it's better/easier to implement a ribbon UI in code or not depends on a few things, like do you want to allow the user to &lt;BR /&gt;
customize your UI (e.g., place standard AutoCAD ribbon controls wherever they want), and/or whether you need custom control &lt;BR /&gt;
functionality that the CUI doesn't support. If the latter isn't required, I would probably take the CUI route, merely because a UI &lt;BR /&gt;
should support basic customization wherever possible.&lt;BR /&gt;
&lt;BR /&gt;
-- &lt;BR /&gt;
http://www.caddzone.com&lt;BR /&gt;
&lt;BR /&gt;
AcadXTabs: MDI Document Tabs for AutoCAD&lt;BR /&gt;
Supporting AutoCAD 2000 through 2010&lt;BR /&gt;
&lt;BR /&gt;
http://www.acadxtabs.com&lt;BR /&gt;
&lt;BR /&gt;
Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");&lt;BR /&gt;
&lt;BR /&gt;
&lt;EBTS&gt; wrote in message news:6310278@discussion.autodesk.com...&lt;BR /&gt;
I'm adding a ribbon tab for our application.  To take full advantage of the ribbon's features, I want to use text, but it will need &lt;BR /&gt;
to be localized to a specific language.  I was wondering what the best method would be to do this.&lt;BR /&gt;
&lt;BR /&gt;
Some options I can think of:&lt;BR /&gt;
a. Create a different partial CUIX file for each language and load the appropriate one.&lt;BR /&gt;
b. Create the ribbon programmatically at run time, using a language specific resource dll with a string table.&lt;BR /&gt;
&lt;BR /&gt;
Anyone know what the accepted practice is for this?  Is there a better option?&lt;/EBTS&gt;</description>
    <pubDate>Thu, 31 Dec 2009 09:24:15 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2009-12-31T09:24:15Z</dc:date>
    <item>
      <title>Localizing the ribbon</title>
      <link>https://forums.autodesk.com/t5/net-forum/localizing-the-ribbon/m-p/2608997#M67758</link>
      <description>I'm adding a ribbon tab for our application.  To take full advantage of the ribbon's features, I want to use text, but it will need to be localized to a specific language.  I was wondering what the best method would be to do this.&lt;BR /&gt;
&lt;BR /&gt;
Some options I can think of:&lt;BR /&gt;
a. Create a different partial CUIX file for each language and load the appropriate one.&lt;BR /&gt;
b. Create the ribbon programmatically at run time, using a language specific resource dll with a string table.&lt;BR /&gt;
&lt;BR /&gt;
Anyone know what the accepted practice is for this?  Is there a better option?</description>
      <pubDate>Wed, 30 Dec 2009 00:11:21 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/localizing-the-ribbon/m-p/2608997#M67758</guid>
      <dc:creator>ebts</dc:creator>
      <dc:date>2009-12-30T00:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Localizing the ribbon</title>
      <link>https://forums.autodesk.com/t5/net-forum/localizing-the-ribbon/m-p/2608998#M67759</link>
      <description>Store the localized strings for multiple locales in an Excel worksheet, using the column containing the English language strings as &lt;BR /&gt;
the key column, and additional columns containing the localized strings for each language, one column for each locale.&lt;BR /&gt;
&lt;BR /&gt;
Then write an XML process that takes the English language CUI file (processing it as an XML file) and the Excel Worksheet, and from &lt;BR /&gt;
that, generate localized CUI files.&lt;BR /&gt;
&lt;BR /&gt;
That would be the easiest way to generate and maintain locale-specific CUI files, and would only require you or the translator to &lt;BR /&gt;
enter data into an Excel worksheet, which is far less error prone than manually editing many CUI files or (gasp) using AutoCAD's CUI &lt;BR /&gt;
dialog.&lt;BR /&gt;
&lt;BR /&gt;
Whether it's better/easier to implement a ribbon UI in code or not depends on a few things, like do you want to allow the user to &lt;BR /&gt;
customize your UI (e.g., place standard AutoCAD ribbon controls wherever they want), and/or whether you need custom control &lt;BR /&gt;
functionality that the CUI doesn't support. If the latter isn't required, I would probably take the CUI route, merely because a UI &lt;BR /&gt;
should support basic customization wherever possible.&lt;BR /&gt;
&lt;BR /&gt;
-- &lt;BR /&gt;
http://www.caddzone.com&lt;BR /&gt;
&lt;BR /&gt;
AcadXTabs: MDI Document Tabs for AutoCAD&lt;BR /&gt;
Supporting AutoCAD 2000 through 2010&lt;BR /&gt;
&lt;BR /&gt;
http://www.acadxtabs.com&lt;BR /&gt;
&lt;BR /&gt;
Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");&lt;BR /&gt;
&lt;BR /&gt;
&lt;EBTS&gt; wrote in message news:6310278@discussion.autodesk.com...&lt;BR /&gt;
I'm adding a ribbon tab for our application.  To take full advantage of the ribbon's features, I want to use text, but it will need &lt;BR /&gt;
to be localized to a specific language.  I was wondering what the best method would be to do this.&lt;BR /&gt;
&lt;BR /&gt;
Some options I can think of:&lt;BR /&gt;
a. Create a different partial CUIX file for each language and load the appropriate one.&lt;BR /&gt;
b. Create the ribbon programmatically at run time, using a language specific resource dll with a string table.&lt;BR /&gt;
&lt;BR /&gt;
Anyone know what the accepted practice is for this?  Is there a better option?&lt;/EBTS&gt;</description>
      <pubDate>Thu, 31 Dec 2009 09:24:15 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/net-forum/localizing-the-ribbon/m-p/2608998#M67759</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-12-31T09:24:15Z</dc:date>
    </item>
  </channel>
</rss>

