Re: [Please Review] Chandler.po

Heikki Toivonen <[email protected]>
Newsgroups gmane.org.osaf.design
Message-ID <[email protected]>
Mimi Yin wrote:
> #: parcels/osaf/framework/MasterPassword.py:452
> msgid "Sensitive information such as email and sharing account
> passwords, are protected with the master password."
> msgstr ""
> *?? Can we just say 'Account passwords are protected...'*

Yes.

> #: parcels/osaf/framework/MasterPassword.py:561
> msgid ""
> "Protected information will be deleted.\n"
> "Are you sure you want to reset Master Password?"
> msgstr ""
> *?? Can we say 'Account passwords will be deleted.'*

Yes.

> #: 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.

> #: 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.

> #: 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.

-- 
  Heikki Toivonen

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

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
signature.asc (application/pgp-signature, 254 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGko0tb8x8KoP+JuwRAhwTAKCHamhP2DqeUqqqCO1ooOQ/6DHMbgCcDedB
zwLiVdgHSjE8Y1GNngZbQ24=
=lkrp
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.