<?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 ISO-8859-2 char set problem in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/iso-8859-2-char-set-problem/m-p/3575030#M6288</link>
    <description>We have a mail list. Some of the newsletters are contains some characters on local language (Hungarian) or p.ex. the apostrophe character. After we are sending that mail it will be converted (encoded) with the iso8859-2 char set automatically, but on the receiver side we see only codes of these special characters (like apostrophe character converted to the „, or to the ” code).&lt;BR /&gt;Could someone explain me this symptom? Could you propose a solution to eliminate the conversions?&lt;BR /&gt;I have lost my knowledge of chat sets and encoding for 5 years.&lt;BR /&gt;&lt;BR /&gt;Regars,&lt;BR /&gt;Zsolt</description>
    <pubDate>Fri, 01 Jul 2005 10:47:33 GMT</pubDate>
    <dc:creator>Zsolt Kukedi_1</dc:creator>
    <dc:date>2005-07-01T10:47:33Z</dc:date>
    <item>
      <title>ISO-8859-2 char set problem</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/iso-8859-2-char-set-problem/m-p/3575030#M6288</link>
      <description>We have a mail list. Some of the newsletters are contains some characters on local language (Hungarian) or p.ex. the apostrophe character. After we are sending that mail it will be converted (encoded) with the iso8859-2 char set automatically, but on the receiver side we see only codes of these special characters (like apostrophe character converted to the „, or to the ” code).&lt;BR /&gt;Could someone explain me this symptom? Could you propose a solution to eliminate the conversions?&lt;BR /&gt;I have lost my knowledge of chat sets and encoding for 5 years.&lt;BR /&gt;&lt;BR /&gt;Regars,&lt;BR /&gt;Zsolt</description>
      <pubDate>Fri, 01 Jul 2005 10:47:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/iso-8859-2-char-set-problem/m-p/3575030#M6288</guid>
      <dc:creator>Zsolt Kukedi_1</dc:creator>
      <dc:date>2005-07-01T10:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISO-8859-2 char set problem</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/iso-8859-2-char-set-problem/m-p/3575031#M6289</link>
      <description>Hi Zsolt,&lt;BR /&gt;it's not clear if your nwesletter has iso8859-2 code or else „ char sequence.&lt;BR /&gt;I think you have to open your newsletter with some software without conversion like notepad to see into.&lt;BR /&gt;When you prepare you newsletter what fonto do you use? Can you write it with UNICODE?&lt;BR /&gt;What font have your receivers?&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Sat, 02 Jul 2005 03:23:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/iso-8859-2-char-set-problem/m-p/3575031#M6289</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-07-02T03:23:31Z</dc:date>
    </item>
  </channel>
</rss>

