Power*Architect - I18N

[Rogerio Ramos]

Hello All

I've to follow all of discussion about new features, refactoring and all about Power*Architect and the base library.
My question is: how to organize or minimize de effort to keep always de translations of the features add in our
tool?
I'd like to keep up-to-date the translations but it too many difficult to follow all changes, there a way to comunicate
the static text changes?


--
Rogério Ramos da Silva
msn: hab...@hotmail.com
skype: habutre
email alternativo: ramos...@ig.com.br

OBS: Qualquer anomalia, irregularidade ou desfiguração de documento anexo, pode dar-se devido a alguma incompatibilidade da suite open source OpenOffice utilizada como alternativa à suite office da Microsoft®

"Fé inabalável é somente
aquela que pode encarar a
razão face-a-face em qualquer
época da Humanidade".

[Jonathan Fuerth]

It's a good question.

Here's my idea: we could add a step to the build that locates
non-internationalized strings, message keys present in the English
file but missing in others, and message keys present in other
languages but missing in English (the latter group would be messages
we're no longer using).

If the output of such a build step was one RSS file per locale (plus
one for the non-i18n strings still in the source code), you could
follow the status of the pt_BR translation (and others) using an RSS
reader.

If that sounds like a good plan, who wants to do it?

Jonathan

> --
> You received this message because you are subscribed to the Google Groups "Architect Developers" group.
> To post to this group, send email to architect-...@googlegroups.com.
> To unsubscribe from this group, send email to architect-develo...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/architect-developers?hl=en.
>

[Rogerio Ramos]

This feature looks like a good improve, I'd can to prepare anything about that.

-Habutre