<?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: Cyrillic client in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/cyrillic-client/m-p/6028924#M1348995</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lawrence,&lt;/P&gt;&lt;P&gt;technically, it should be possible to transfer the client to another system, do the conversion and copy it back to your main Unicode system.&lt;/P&gt;&lt;P&gt;However:&lt;/P&gt;&lt;P&gt;1) This will certainly add time to your downtime,  client export and import cannot be done in uptime ...&lt;/P&gt;&lt;P&gt;2) How do you handle client independent data - like e.g. report texts ?&lt;/P&gt;&lt;P&gt;3) As far as I know, none or only a few customers have chosen this approach - so there are probably more issues and it is  not tested ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand side many customers have used successfully transaction SPUMG for an MDMP conversion.&lt;/P&gt;&lt;P&gt;In addition, it will be very easy for you to distinguish between Russian and Latin-1 in the vocab and reprocessing logs  ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore I would recommend to use the standard tools (SPUMG and SUMG).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Nils Buerckel&lt;/P&gt;&lt;P&gt;SAP AG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Aug 2009 06:11:41 GMT</pubDate>
    <dc:creator>nils_buerckel</dc:creator>
    <dc:date>2009-08-19T06:11:41Z</dc:date>
    <item>
      <title>Cyrillic client</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cyrillic-client/m-p/6028923#M1348994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have another idea and just would like some feedback if its feasable or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are converting to unicode and the our issues come from the &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cyrillic code page..  1500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since this code page is unique to only 1 client,  would&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It be possible to build a u201CMigrationu201D system with this client only .. Then convert  the "cyrillic client" to unicode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eliminating the possibility of false language assignment.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then importing the converted unicode client back to the Master UC system (which only contained latin-1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lawrence&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Aug 2009 15:59:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cyrillic-client/m-p/6028923#M1348994</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-18T15:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cyrillic client</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cyrillic-client/m-p/6028924#M1348995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lawrence,&lt;/P&gt;&lt;P&gt;technically, it should be possible to transfer the client to another system, do the conversion and copy it back to your main Unicode system.&lt;/P&gt;&lt;P&gt;However:&lt;/P&gt;&lt;P&gt;1) This will certainly add time to your downtime,  client export and import cannot be done in uptime ...&lt;/P&gt;&lt;P&gt;2) How do you handle client independent data - like e.g. report texts ?&lt;/P&gt;&lt;P&gt;3) As far as I know, none or only a few customers have chosen this approach - so there are probably more issues and it is  not tested ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand side many customers have used successfully transaction SPUMG for an MDMP conversion.&lt;/P&gt;&lt;P&gt;In addition, it will be very easy for you to distinguish between Russian and Latin-1 in the vocab and reprocessing logs  ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore I would recommend to use the standard tools (SPUMG and SUMG).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Nils Buerckel&lt;/P&gt;&lt;P&gt;SAP AG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Aug 2009 06:11:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cyrillic-client/m-p/6028924#M1348995</guid>
      <dc:creator>nils_buerckel</dc:creator>
      <dc:date>2009-08-19T06:11:41Z</dc:date>
    </item>
  </channel>
</rss>

