Move to Maketext: request for comments

Vitaly Fedrushkov fedrushkov at
Sun Nov 30 07:45:43 UTC 2008

Mikhail Gusarov wrote:

> Bugzilla/* means Linux packagers will have to separate po files to
> another directory, as it contains only Perl code for now, and code goes
> to /usr/lib/perl5/...

Agreed, valid reason for not going this way.

> default/custom separation is from the days when no flexible version
> control systems existed, IMHO. Personally I have no problem maintaining
> a customizations on top of default/* hierarchy under git.

And what about per-project and per-extension templates?

>  VF> * Is Locale::Maketext::Fuzzy practical?

> Will create entries for special cases (and special cases
> will grow in combinatorial numbers)? If not, then it will be hard to
> use.

Well, when the code to 'say' a full sentence is long and sophisticated 
(as can be seen in "auth_failure" error message), it may be practical to 
wrap the entire snippet with [% |l %]...[% END %] instead of having 
trouble of single words translated without context. will not help here, for obvious reasons.  I'd suggest pseudo 
comments putting together variants of text generated by this code snippet.

These variants may be addressed by old good static lexicon entries (yes 
they may grow in combinatorial numbers) or by fuzzy entries.  As these 
will emerge in predictably MUCH less numbers than static entries, 
perhaps we may keep TWO lexicons, 'static' and 'fuzzy', and use explicit 
  fuzzy calls like '[% |l_fuzzy %]...[% END %].

This would save us from 'charge of the light brigade': iterating through 
thousands of keys each time fuzzy match is required.
dev-apps-bugzilla mailing list
dev-apps-bugzilla at

More information about the developers mailing list