Hello All,
EG was my first big project on translation.
IMHO I found that launchpad, like any other online plataform,
that I have used, could only be used for very small projects,
or for corrections and maintaining.
Launchpad, is really solid, and has a good interface.
To work on Begin a big .po,
We didn't use the translations.launchpad at all, because over 6 months
ago when we were starting our localization phase for EG 2.2, I was told
that nobody updates those launchpad files and they are ancient. I could
get the most recent .pot's from the source. Also we couldn't use the
launchpad s
On Tue, Oct 23, 2012 at 11:00:47AM +, Kivilahti Olli-Antti wrote:
> Thanks for your reply Dan!
>
> What I mean with "can't be localized":
> We have been doing our localization according to the instructions here
> http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-admin:customizations:i18n
Thanks for your reply Dan!
What I mean with "can't be localized":
We have been doing our localization according to the instructions here
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-admin:customizations:i18n
We have translated all of the generated .po -files and none of them
affect our
On Mon, Oct 22, 2012 at 11:10 AM, Kivilahti Olli-Antti
wrote:
> Howdy hou Evergreensters! (sorry bshum)
> It looks like the new TPAC can't really be localized and we are planning
> to start making it localizable using the existing gettext tools. Anyone
> working on that yet?
Can you please explai
Howdy hou Evergreensters! (sorry bshum)
It looks like the new TPAC can't really be localized and we are planning
to start making it localizable using the existing gettext tools. Anyone
working on that yet?
We are planning to start work on the matter on 11.11. So far we have
encountered unlocaliz
