You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Andrew Wetmore <an...@apache.org> on 2020/05/12 13:21:56 UTC

Translation query

Hi:

I am trying to assemble a list of translation/localization tools that
Apache projects have had good experiences with. Someone mentioned that the
Directory project provides some translated materials, so I wondered if I
could find out what tool(s) you use and what your experience with them has
been.

Thanks in advance!

Andrew

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andreww@apache.org

Re: Translation query

Posted by Emmanuel Lécharny <el...@gmail.com>.
On 12/05/2020 22:47, Stefan Seelmann wrote:
> Hi Andrew,
>
> On 5/12/20 3:21 PM, Andrew Wetmore wrote:
>> I am trying to assemble a list of translation/localization tools that
>> Apache projects have had good experiences with. Someone mentioned that the
>> Directory project provides some translated materials, so I wondered if I
>> could find out what tool(s) you use and what your experience with them has
>> been.
> I'm only aware that our "Studio" provides some translations, where I can
> give you some details.


FTR, the LDAP API and ApacheDS ae also following the same path, with 
FR/US/DE languages being suipported by ApacheDS (the LDAP API is only 
supporting EN atm).

>
> Studio is based on the Eclipse framework. For all the components we
> reuse from Eclipse (standard menus and dialogs, preferences) we just use
> the translation packages they provide.
>
> For our own plugins we follow the Eclipse approach and use so-called
> resource bundles which means that there is one properties file per
> language for each plugin and each Java package. This is quite messy
> because all the translations are spread across hundreds of files.
>
> We currently provide 3 languages: English, French, German. That's by
> coincidence the languages the developers speak ;). But AFAIK we never
> reached out to the community to provide more translation.
>
> I personally don't use any particular tool to do translations but just
> edit the properties files directly.
>
> I hope that helps, I'm happy to answer more questions :)
>
> Kind Regards,
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
> For additional commands, e-mail: dev-help@directory.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org

Re: Translation query

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 5/13/20 6:52 PM, Andrew Wetmore wrote:
> Thank you, Stefan. I am quite familiar with resource bundles, and have
> worked with them for many years in Flex (and now Apache Royale) apps.
> 
> Am I correct that you guys are dealing with a relatively small number of
> strings, as for error messages and button labels, but no translated
> documentation?

Yes, correct. The documentation that is published via the website and in
the Eclipse integrated browser only exists in English. The source are
docbook XML files that then are transformed to HTML and PDF.

Kind Regards,
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org

Re: Translation query

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Hi Andrew,

On 5/12/20 3:21 PM, Andrew Wetmore wrote:
> I am trying to assemble a list of translation/localization tools that
> Apache projects have had good experiences with. Someone mentioned that the
> Directory project provides some translated materials, so I wondered if I
> could find out what tool(s) you use and what your experience with them has
> been.

I'm only aware that our "Studio" provides some translations, where I can
give you some details.

Studio is based on the Eclipse framework. For all the components we
reuse from Eclipse (standard menus and dialogs, preferences) we just use
the translation packages they provide.

For our own plugins we follow the Eclipse approach and use so-called
resource bundles which means that there is one properties file per
language for each plugin and each Java package. This is quite messy
because all the translations are spread across hundreds of files.

We currently provide 3 languages: English, French, German. That's by
coincidence the languages the developers speak ;). But AFAIK we never
reached out to the community to provide more translation.

I personally don't use any particular tool to do translations but just
edit the properties files directly.

I hope that helps, I'm happy to answer more questions :)

Kind Regards,
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org