[Chandler-dev] Branding (as in how to do it in code), i18n/l10n

Heikki Toivonen heikki at osafoundation.org
Wed May 31 12:40:38 PDT 2006


Yesterday we discussed the ab ability to brand Chandler when I realized
there is currently no easy way to do it.

At a minimal level there should be a way to replace the vendor string,
the application name string, application icons/images and welcome note
text. If you wanted to get beyond that you would get into full
skinnability etc. but I don't think this is initially required.

I was hoping we could utilize the i18n support we've built in (as far as
I remember Mozilla does this for browser name etc.), but unfortunately
these brand dependent strings are needed before we have opened the
repository. We have this same problem in displaying error dialogs to
users in case we have a problem opening the repository.

So I was thinking that we need some i18n support during the bootstrap
process.

There is a wrinkle, though, and that is that a brand is not a locale,
which is how translation normally happens. You should be able to use the
same brand in several different locales. Quick look at Python gettext
did not seem to indicate anything that would be directly usable. Anyone
know if it supports it or if there is something else we could use?

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060531/f5b693ae/signature.pgp


More information about the chandler-dev mailing list