[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
rfc: handling translations for i18n support
From: |
William Hubbs |
Subject: |
rfc: handling translations for i18n support |
Date: |
Thu, 26 Aug 2010 22:31:16 -0500 |
On Thu, Aug 26, 2010 at 10:48:31PM +0100, Rui Batista wrote:
> Hi,
> Qua, 2010-08-25 ??s 22:03 -0500, William Hubbs escreveu:
> > On Wed, Aug 25, 2010 at 12:35:02AM +0100, Rui Batista wrote:
> > > This patch adds intltool/gettext support to the build infrastructure.
> > > From noone, files marked for translation shuld be listed in
> > > po/POTFILES.in.
> >
> > I would vote against this patch for thoe following reasons:
> >
> > - it does not update README to reflect the need for intltool/gettext
> > - it does not include any documentation telling translators how to get
> > their translations into the project.
> >
> You're right, maybe it is better to provide those one patch. I'll base
> the documentation on documentation I wrote for OpenTTS.
> Note that the INSTALL file, that I need to update to reflect
> intltool/gettext, is very outdated. I'll write a patch to update it
> before anything.
Also, I think we need to have a procedure for handling translations so
that we can document how we want translations submitted in the patch.
What does everyone think would be a good way to handle them? Should we
just have translators email their translations to the list?
William
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://lists.freebsoft.org/pipermail/speechd/attachments/20100826/a53de1d4/attachment.pgp>
- rfc: handling translations for i18n support,
William Hubbs <=