<?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 Best practices for using Feature Services in multiple languages in Web AppBuilder in ArcGIS Web AppBuilder Questions</title>
    <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354285#M9406</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to localize my apps in two languages: my native language (Estonian), and English. While the localization of widgets and themes can be achieved easily with the use of nls files, I was wondering how to best localize Feature Services. I'd want to display the Feature Services' attribute information in the pop-ups&amp;nbsp;and attribute tables in&amp;nbsp;both&amp;nbsp;languages (that is, in Estonian for&amp;nbsp;apps that have their UI in Estonian, and in English for apps that have their UI in English).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can think of a few ways how to&amp;nbsp;achieve this:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;displaying&amp;nbsp;the translation to English in brackets for text fields&lt;/STRONG&gt;: &lt;EM&gt;&amp;lt;text in Estonian&amp;gt; (&amp;lt;text in English&amp;gt;)&lt;/EM&gt;&lt;BR /&gt;This&amp;nbsp;is the easiest solution but not the most elegant and could get messy for longer texts.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;creating extra fields for the translations to English and hiding unnecessary fields for pop-ups and attribute tables with JavaScript&lt;/STRONG&gt;&lt;BR /&gt;The best solution that I can think of but hiding the fields could get a little tricky.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;creating extra services with&amp;nbsp;attribute information in English&lt;BR /&gt;&lt;/STRONG&gt;Again a simple solution but this could take the memory consumption of my services through the roof if the number of services grew.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any other and smarter options available?&amp;nbsp;All opinions are very appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Jan 2017 20:42:02 GMT</pubDate>
    <dc:creator>MihkelMänna</dc:creator>
    <dc:date>2017-01-09T20:42:02Z</dc:date>
    <item>
      <title>Best practices for using Feature Services in multiple languages in Web AppBuilder</title>
      <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354285#M9406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to localize my apps in two languages: my native language (Estonian), and English. While the localization of widgets and themes can be achieved easily with the use of nls files, I was wondering how to best localize Feature Services. I'd want to display the Feature Services' attribute information in the pop-ups&amp;nbsp;and attribute tables in&amp;nbsp;both&amp;nbsp;languages (that is, in Estonian for&amp;nbsp;apps that have their UI in Estonian, and in English for apps that have their UI in English).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can think of a few ways how to&amp;nbsp;achieve this:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;displaying&amp;nbsp;the translation to English in brackets for text fields&lt;/STRONG&gt;: &lt;EM&gt;&amp;lt;text in Estonian&amp;gt; (&amp;lt;text in English&amp;gt;)&lt;/EM&gt;&lt;BR /&gt;This&amp;nbsp;is the easiest solution but not the most elegant and could get messy for longer texts.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;creating extra fields for the translations to English and hiding unnecessary fields for pop-ups and attribute tables with JavaScript&lt;/STRONG&gt;&lt;BR /&gt;The best solution that I can think of but hiding the fields could get a little tricky.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;creating extra services with&amp;nbsp;attribute information in English&lt;BR /&gt;&lt;/STRONG&gt;Again a simple solution but this could take the memory consumption of my services through the roof if the number of services grew.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any other and smarter options available?&amp;nbsp;All opinions are very appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2017 20:42:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354285#M9406</guid>
      <dc:creator>MihkelMänna</dc:creator>
      <dc:date>2017-01-09T20:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for using Feature Services in multiple languages in Web AppBuilder</title>
      <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354286#M9407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mihkel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;I have never had to worry about this, but if I were in your situation I believe I would tackle #2 (hiding the fields). Well actually dynamically switching the popuptemplate for the layer based on the locale.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2017 20:51:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354286#M9407</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2017-01-09T20:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for using Feature Services in multiple languages in Web AppBuilder</title>
      <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354287#M9408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for answer, Robert!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Switching the popuptemplate is a great idea! I'll certainly give it a try!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2017 20:57:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-web-appbuilder-questions/best-practices-for-using-feature-services-in/m-p/354287#M9408</guid>
      <dc:creator>MihkelMänna</dc:creator>
      <dc:date>2017-01-09T20:57:27Z</dc:date>
    </item>
  </channel>
</rss>

