Oliver, I have just sent a new (simplified) version of the patch to Michael. It goes along with his advice brought up this morning. Please find a copy of my message below. The new ver of a patch is available from:
http://openca.narod.ru/ All the best, Sergei ================================== Dear Michael, >I started to check your patch. I looked into the character set selector and I >asked me why did you not integrate it like a normal config option into >config.xml? A good solution would be __DEFAULT_ENCODING__ or >__DEFAULT_CHARSET__. The configfiles would include @__DEFAULT_CHARSET__@ and >after configure_etc.sh all files have the appropriate encoding. I want to >integrate the change as seemless as possible. Actually we did. config.xml has new option "cert_chars" with values UTF8 or LATIN1. I thought that we have to differentiate it from already present default_language and default_charset. >The selector is of course much faster than configure_etc.sh but it is another >configtool and OpenCA is not really easy to install. utf8-latin1-selector normally was called exactly from inside configure_etc.sh. Ability to call it from console was a bonus for those who want it. >So I want to minimize the steps. Nevertheless the openssl-setopt tool is cool. >I will at minimum integrate it into the head but the 0.9.2 patch should >minimize the intrusive character of the patch. If we can integrate the >encoding only as a new option in config.xml then this would be optimal for the >most users (of course you did much more in the background but the user only >see one option in config.xml). > > >It looks for me like all files which will be touched by the encoding selector >have *.template sources. Another thing is that we have not to duplicate the >config files. Agreed. Attached please find a patch which supposes just 2 steps from the user: 1) edit config.xml (option cert_chars" with values UTF8 or LATIN1) 2) run configure_etc.sh To diminish psychological impact now utf8-latin1-selector is always called from configure_etc.sh and is not supposed to run from the console. So it is hidden from the user as you want. Multiple utf8-enabled config files along with templates are absent altogether. All "names" in cert and reqs have type @[EMAIL PROTECTED] (case is not important) to be fixed by configure_etc.sh as you suggested. Somehow changed nearly all files, so please use new copies. All the best, Sergei ================================================================= At 19:32 02.08.2005, you wrote: >Hi Sergei, > >I put the HowTo's on mysql and postgresql on the website - mayn thanks for >this. We are currently discussion what to do with the utf8 patch, we will >either put it into 0.9.2.3 release or create a new "patches" section on the >website where we will list it. > >Additional I am prepareing a new section with links to external sites where we >will list yours. > >best regards > >Oliver >-- >Diese Nachricht wurde digital unterschrieben >oliwel's public key: http://www.oliwel.de/oliwel.crt >Basiszertifikat: http://www.ldv.ei.tum.de/page72 > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Openca-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openca-users
