<?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: Encoding for localization in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191618#M144748</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;@jbarrez,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I meant that when new messages_SOMELANG.properties file is created, the actual encoding should be in uniqode. Which is not conenient. I think that UTF8 would be the better approach for properties file.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 19 Oct 2014 04:20:13 GMT</pubDate>
    <dc:creator>sav1</dc:creator>
    <dc:date>2014-10-19T04:20:13Z</dc:date>
    <item>
      <title>Encoding for localization</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191616#M144746</link>
      <description>Which encoding should I use to localize Activity Explorer?I tried windows-1251, utf-8, but when activity web login page is opened the text is not readable.</description>
      <pubDate>Wed, 15 Oct 2014 01:16:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191616#M144746</guid>
      <dc:creator>sav1</dc:creator>
      <dc:date>2014-10-15T01:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: Encoding for localization</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191617#M144747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;How do you mean 'not readable'. UTF-8 should be fine.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Oct 2014 09:51:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191617#M144747</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-10-17T09:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Encoding for localization</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191618#M144748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;@jbarrez,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I meant that when new messages_SOMELANG.properties file is created, the actual encoding should be in uniqode. Which is not conenient. I think that UTF8 would be the better approach for properties file.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Oct 2014 04:20:13 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191618#M144748</guid>
      <dc:creator>sav1</dc:creator>
      <dc:date>2014-10-19T04:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Encoding for localization</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191619#M144749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You mean files like &lt;/SPAN&gt;&lt;A href="https://github.com/Activiti/Activiti/blob/master/modules/activiti-explorer/src/main/resources/messages_de.properties" rel="nofollow noopener noreferrer"&gt;https://github.com/Activiti/Activiti/blob/master/modules/activiti-explorer/src/main/resources/messages_de.properties&lt;/A&gt;&lt;SPAN&gt; ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;They open fine for me (mac) … but that doesn't prove anything. How do these files look for you?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Oct 2014 09:19:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/encoding-for-localization/m-p/191619#M144749</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-10-20T09:19:31Z</dc:date>
    </item>
  </channel>
</rss>

