Re: I18N text domains for zopeproducts

On Tuesday 12 August 2003 23:25, Fred L. Drake, Jr. wrote:
> In a checkin message, Stephan Richter wrote:
>  > Add domain to templates.
> ...
>  > +  i18n:domain="zope">
>
> I think we need to think about what the "right" domain is for the
> extra products in the zopeproducts directory.

Note that this domain was added there, so it can reuse Zope 3's translations, 
which is very sensible in my opinion.

> The question is one of how these components will be distributed, and
> what the unit of composition will be when building a site.  Will all
> of these always be part of a Zope 3 distribution?  If not, these
> should not share the "zope" text domain.

No, not all. But the Bug Tracker (where this check in is coming from) will 
always depend heavily on zope.app. And that will never change.

> I think each separate component (as in "installable pile of software")
> should have a separate domain.  We should determine some guidelines to
> make recommendations as to how text domain names should be created
> for separate components.

Mmh, I disagree. This really encourages a lot of duplication in translations. 
On the other hand, one could argue that there should be tools that detect 
equal translations and fill them in automatically before someone even starts 
to translate. Note that this is the type of functionality our Web-based 
translation manager should handle (if you do not know what I am talking 
about, ask Barry). 

http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/
TranslationWebService

Regards,
Stephan
-- 
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training