> > The minimum is variable because some key modes exist that require a > > certain length passphrase, but none of them have been implemented yet. > > The 8 character limit is in fact quite artificial and will likely be > > replaced by a more precise per-cipher/crypt_type limit eventually. > > > > For the moment I think we could simply drop the variable if it makes > > translator's lifes more difficult. If it's not too bad, perhaps we could > > also live with the (probably minor?) inaccuracy in translations. Both > > options are fine with me, let me know what you prefer. > > I think the variable can stay, as it will be introduced back later on > (no need to redo work), and add a comment that the string should be > translated as if the value would be 8.
Comment added. > > I am not sure how one could deal with the later change (adding the > fuzzy attribute) when it will be necessary, if the string itself did > not change (maybe adding an artificial space?) but only the comment. *that* is easy...add a fake space, run the PO update and then remove it... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
