On first try, I used ro_RO as default language on both systems. I tried now with en_GB, but the result was almost the same (except garbled characters on diacritics used in html translation on steps 4, 6 and 8 - wherever � appeared in CN). I took some screenshots when using en_GB and handling 2 requests:
1. CSR - New - on RA interface http://img185.imageshack.us/img185/8360/racsrnewengb.png 2. CSR - Approved - on RA interface (they were approved without signing, from the same reason mentioned by __bliss) http://img340.imageshack.us/img340/2769/racsrapprovedengb.png 3. CSR - Approved - on CA interface, after dataexchange (notice that now both look ok here) http://img340.imageshack.us/img340/1045/cacsrapproved1engb.png 4. CSR - Details - on CA interface, from the first request; here the CN looks different, � instead of diacritic http://img441.imageshack.us/img441/4292/cacsrapproveddetail1eng.png 5. CSR - Details - on CA interface, from the second request; the CN looks ok, even if the same diacritic from the first request appear in here http://img221.imageshack.us/img221/8957/cacsrapproveddetail2eng.png 6. CSR - Issue certificate - on CA interface, when trying to issue the first certificate http://img682.imageshack.us/img682/4061/caissuedetail1engb.png 7. CSR - Issue certificate - on CA interface, when trying to issue the second certificate http://img260.imageshack.us/img260/7728/caissuedetail2engb.png 8. CSR - Approved - on CA interface, after successfully issuing the second certificate, the � character appears on this page too http://img339.imageshack.us/img339/5682/cacsrapproved2engb.png On Sat, Mar 20, 2010 at 12:10 PM, Massimiliano Pala <p...@cs.dartmouth.edu> wrote: > I did some fixes... I noticed that if your default language in the node is > set to "C" instead of any other language, then the sent encoding is > ISO-8859-1, > and if you have some requests/certificates with utf-8 characters they do not > get displayed correctly. > > A suggestion: change your default language to en_GB (or any other but "C"). > > Cheers, > Max > > > On 03/19/2010 07:18 AM, __bliss wrote: >> >> Well, problems tend to go on... :( I successfully requested a certificate >> at >> the public interface (but failed to sign it: all passwords i've ever typed >> in failed, so did pin verification; nevertheless, the request was >> approved( >> http://old.nabble.com/file/p27950939/spkac.png spkac.png ). On uploading >> data to CA data appeared in unreadable symbols( >> http://old.nabble.com/file/p27950939/ra2.png ra2.png >> http://old.nabble.com/file/p27950939/ra3.png ra3.png ) and attempt to >> issue >> a certificate failed -- unreadable symbols prevent even tries to >> understand >> what is wrong... ( http://old.nabble.com/file/p27950939/ra4.png ra4.png )) > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Openca-Users mailing list > Openca-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openca-users > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
