i18n of bzr

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
> 2) There is "wrong" design decision in bzr itself to put help for
> commands in the class docstrings. This decision today is main
> show-stopper for localizing these helps. Docstrings should be converted
> to plain strings first, i.e. major API break of commands required. This
> is a lot of work.
> Furthermore it affects most of existing plugins.

^- I'll note that we did something similar with exception strings
(switching from __doc__ to _fmt = ) and it wasn't terribly traumatic.
Just needs someone who cares enough to do so for commands.

Though I'll note that the actually documentation for commands comes from
running the 'Command.help()' function. This is because stuff like
dynamic registries, see-also, etc all lead to a lot more than can be put
into a static __doc__ string.

I think we build the man page, etc, by enumerating all known commands
and then grabbing their help strings.

I really don't have a great answer for what you would want for
translations. Just doing the __doc__ strings would probably get you
reasonably far, though.

John
=:->


> 
> 3) Testing? I think any special testing for i18n can be omitted. If
> existing tests check english texts -- they should continue to do so. But
> special tests for ensure i18n works will be nightmare.
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksBeqYACgkQJdeBCYSNAANCUwCg2VR+E/fAxlksD7Eapl6TDc6X
AvMAn2nhYD+t09FF9H/5wTQWBdfwdISn
=6L8P
-----END PGP SIGNATURE-----