<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>olat developers - shell tag</title>
  <link>http://blogs.frentix.com/blogs/development/tags/shell/</link>
  <description>Java, JavaScript, CSS, HTML and OLAT development news</description>
  <language>de</language>
  <copyright>frentix GmbH</copyright>
  <lastBuildDate>Mon, 30 Jul 2007 11:49:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Dealing with encoding issues</title>
    <link>http://blogs.frentix.com/blogs/development/2007/01/29/1170090540000.html</link>
    
      
      
        <description>
          Porting an OLAT installation from a Windows to a Linux server can produce many encoding issues. Windows uses normally Windows-1252 AKA CP1252 encoding and Linux nowadays often uses UTF-8.&lt;br /&gt;
&lt;br /&gt;
It is not possible to just move the files from the Windows server to the Linux server, filenames that contain &amp;auml;&amp;ouml;&amp;uuml; will all have ??? instead. &lt;br /&gt;
&lt;br /&gt;
Read the entire article to learn what the common pitfalls are and how you can solve them.&lt;br /&gt;&lt;p&gt;&lt;a href=&#034;http://blogs.frentix.com/blogs/development/2007/01/29/1170090540000.html&#034;&gt;Mehr...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>Shell tricks</category>
    
    <category>OLAT</category>
    
    <comments>http://blogs.frentix.com/blogs/development/2007/01/29/1170090540000.html#comments</comments>
    <guid isPermaLink="true">http://blogs.frentix.com/blogs/development/2007/01/29/1170090540000.html</guid>
    <pubDate>Mon, 29 Jan 2007 17:09:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
