Nightly 20070202 and new encoding switch

[Toby Johnson]

Constantine Dokolas wrote:
> Dirk <vss2svn <at> nogga.de> writes:
>
>   
>> You are right. Sadly Perl does not provide all encodings 
>>
>> The README in Perls encoding directory states the following:
>>
>>     
>>> This directory contains binary encoding maps for some selected encodings.
>>> If they are placed in a directoy listed in 
>>>  <at> XML::Parser::Expat::Encoding_Path,
>>> then they are automaticly loaded by the XML::Parser::Expat::load_encoding
>>> function as needed. Otherwise you may load what you need directly by
>>> explicity calling this function.
>>>
>>> These maps were generated by a perl script that comes with the module
>>> XML::Encoding, compile_encoding, from XML formatted encoding maps that
>>> are distributed with that module. These XML encoding maps were generated
>>> in turn with a different script, domap, from mapping information contained
>>> on the Unicode version 2.0 CD-ROM. This CD-ROM comes with the Unicode
>>> Standard reference manual and can be ordered from the Unicode Consortium
>>> at http://www.unicode.org. The identical information is available on the
>>> internet at ftp://ftp.unicode.org/Public/MAPPINGS.
>>>
>>>       
>> With this information at hand I searched Google and found a 
>> windows-1252.xml file that I copied and manually edited to describe the 
>> windows-1253 codepage (http://en.wikipedia.org/wiki/Windows-1253). Here 
>> are the two files. Try to use them. Perhaps you will have better luck. 
>> If it still fails generating the proper characters, please check the 
>> windows-1253.xml file. I could be possible that I made a mapping error.
>>
>> Attachment (windows-1253.enc): application/octet-stream, 1072 bytes
>> Attachment (windows-1253.xml): text/xml, 1280 bytes
>>     
>
> I droped these files into the same directory as the EXEs and everything 
> worked fine. The filenames get transfered correctly. The only error I still 
> get is for the ini file for the parser, but that doesn't seem to have an 
> impact.
>
> I will keep an eye for the next version and I'll try to keep you posted. :)
>
> I may try the transfer on a bigger/more important repository later if there 
> is interest from the higher powers (this one got me a 350M dump file).
>
> Anything you would like me to report on?
>
> Thanks all (for the new encoding feature, the help, and the enc file),
>   

Great job guys... perhaps we should make those files available in the 
contrib area? Or perhaps the author of XML::Encoding would be interested 
in them?

I have created a FAQ entry for Encoding issues which points here:
<http://www.pumacode.org/projects/vss2svn/wiki/VssEncodingIssues>

Dirk, do you think you could write up a quick recipe for this page, with 
more specific commands on how you created this encoding?

toby