Re: [Please Review] Chandler.po

Hi Heikki, Thx for the speedy reply...

On Jul 9, 2007, at 12:31 PM, Heikki Toivonen wrote:

>> #: parcels/osaf/framework/certstore/dialogs.py:160
>> msgid ""
>> "This certificate is already known but not trusted.\n"
>> "Do you want to trust this certificate?\n"
>> "SHA1 fingerprint: %s"
>> msgstr ""
>> *?? Can we say 'You have previously chosen not to trust this
>> certificate. Do you want to trust this certificate now?'*
>
> I'd rather not make this change, as it may not be accurate to say that
> the user chose to not trust this certificate earlier.

What are other ways in which a certificate can be known? Just trying  
to look for ways to make that part of the sentence a bit more  
concrete. Simply 'This certificate is already known...' feels kind of  
spooky cuz there's no knower and there's no explanation of how the  
knower came to know.

>
>> #: parcels/osaf/framework/certstore/errors.py:24
>> #: parcels/osaf/framework/certstore/errors.py:51
>> msgid "Unable to get issuer certificate."
>> msgstr ""
>> *?? What's an issuer? Is it the 'Issuer-Certificate' field?  
>> 'Unable to
>> get issuer-certificate field.'*
>
> All certificates are issued by somebody. The issuer also has a
> certificate (=issuer certificate). This error is saying that we could
> not find the issuer's certificate for the certificate that we are
> currently checking for correctness. So what the current text is saying
> is correct.

How do we know about the issuer without knowing about their  
certificate? Or I guess what is the issuer to the user? A sharing  
service? ISP? Another user? Could we say: Unable to get certificate?  
I'm wondering if we're effectively saying: Unable to get the  
certificate-originator's certificate; which feels redundant.

Same issue with below.

>
>> #: parcels/osaf/framework/certstore/errors.py:26
>> msgid "Unable to decode issuer public key."
>> msgstr ""
>> *?? Can we say 'Unable to decode public key.'*
>
> No, that would change the meaning, or at least make it ambiguous.
>
>> #: parcels/osaf/framework/certstore/errors.py:30
>> msgid "Format error in certificate's notBefore field."
>> msgstr ""
>> #: parcels/osaf/framework/certstore/errors.py:31
>> msgid "Format error in certificate's notAfter field."
>> msgstr ""
>> *?? Can we say 'Certificate start time / end time is formatted
>> incorrectly.'*
>
> It might not be strictly correct to change it to that wording. The
> notBefore/notAfter fields are very clear in what is wrong. Also,  
> all of
> the error strings in error.py come directly from OpenSSL, so it is
> likely there already are ready translations for these strings  
> somewhere.

It just took me a while to understand that notBefore/notAfter  
referred to time limits on the certificate. Do you have any ideas on  
how to phrase this error message without using technical terminology?  
Is time limit an accurate way to describe the notBefore and notAfter  
settings?

>
> -- 
>   Heikki Toivonen
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design