Re: [Rosegarden-devel] Rosegarden translation to pt_BR

[Helio C. de C. <he...@kd...>]

Hi=20

Silvan, i can help Samuel if he needed.

Samuel, eu sou desenvolvedor do projeto KDE e j=E1 tenho um pouco de manha =
sobre=20
tradu=E7=E3o ( s=F3 n=E3o traduzi o Rosegarden porque n=E3o deu tempo mesmo=
 )
Se tu precisares de ajuda com o KBabel, =E9 s=F3 dar um grito.

[]'s

On Thursday 28 October 2004 22:19, Silvan wrote:
> On Thursday 28 October 2004 07:52 pm, Samuel Pecci wrote:
> > Greetings,
> >
> >    From my ramblings with Rosegarden so far, I guess this is the right
> > list to post this. I would like to submit a translation file for locale
> > pt_BR (Brazilian Portuguese). Could the people involved give me
> > directions on how to do it?
>
> Grab a CVS tree (or a tarball...  we're trying very hard not to change
> strings right now, so it should be the same I guess) and have a look at
> this (pasted straight out of the file):
>
> ->cat rosegarden/docs/howtos/translation.txt
> How to make a new translation for Rosegarden :
>
> - run './scripts/update_i18n_messages' from the top-level directory to
> ensure messages are up to date. This will update the 'rosegarden.pot'
> file in the po/ directory.
>
> - go to the po/ directory, copy 'rosegarden.pot' to the new xx.po file
> you want to translate, for instance fr.po
>
> - back to the top level, run 'make -f Makefile.cvs ; ./configure' (or
> your preferred xx_configure wrapper script). This will refresh
> po/Makefile so the new .po file will be taken into account.
>
> - From now on, a 'make' in po/ will compile the message files into
> .gmo files, and 'make package-messages' at top-level will update the
> new po files with newly found messages as well.
>
> XEmacs has a very good mode for po edition, but it doesn't know how to
> deal with UTF-8 chars, and you have to stick to UTF-8 :
>
> http://i18n.kde.org/translation-howto/
>
> So KBabel (from the kdesdk module) is in fact a much better tool.
>
> IMPORTANT NOTE : DO NOT USE QString CONCATENATION TO CREATE MESSAGES,
> ALWAYS USE .arg().
>
> E.g. this is WRONG :
>
> QString message =3D i18n("Can't open file ") + filename;
>
> And this is RIGHT :
>
> QString message =3D QString(i18n("Can't open file %1")).arg(filename);

=2D-=20
Helio Chissini de Castro
KDE Developer
Brasil/South America Primary Contact