Adam GROSZER wrote:
Though no idea how the above could be solved with FOSS tools.
You know Launchpad is being open sourced, right?
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
2009/2/10 Paul Winkler sli...@gmail.com:
On Tue, Feb 10, 2009 at 01:54:54PM +0100, Martijn Faassen wrote:
In my mind, the Zope framework should offer facilities to support
translating applications. These applications can be composed out of more
than a single package, and we want to support the
2009/2/10 Martijn Faassen faas...@startifact.com:
+1 also to have a way to *see* the translations as a single whole, with
the possibility to define a message id that is used by many packages.
I'm not sure about the last thing. Message objects are bound to one
translation domain, so the
On Monday 09 February 2009, Adam GROSZER wrote:
There are proprietary tools to enforce this. I think launchpad
translation is somehow also a translation memory as it pulls in
previous translations.
Though no idea how the above could be solved with FOSS tools.
KDE's KBabel has support for
Hello,
Yeah, after a quick check it's superseeded by Lokalize which in turn
seems to have also Translation memory and Glossary, where glossary
looks like the termbase support.
http://docs.kde.org/development/en/kdesdk/lokalize/glossary.html
Tuesday, February 10, 2009, 9:01:49 AM, you wrote:
SR
2009/2/10 Adam GROSZER agros...@gmail.com:
In short, a good translation is consistent.
That means the same sentences are translated to the same foreign
sentence. A so-called translation memory is used for that.
Also terms (specific words or expressions of the domain) are
translated to the
Hey,
+1 for getting rid of zope.app.locales as a centralized point for
translations.
+1 also to have a way to *see* the translations as a single whole, with
the possibility to define a message id that is used by many packages.
I'm not sure I get all the details. One question is whether
On Tue, Feb 10, 2009 at 01:54:54PM +0100, Martijn Faassen wrote:
In my mind, the Zope framework should offer facilities to support
translating applications. These applications can be composed out of more
than a single package, and we want to support the translation memory
usecase for that.
On Monday 09 February 2009, Dan Korostelev wrote:
Nowadays, when we have a fully egg-based setup, the translations in
the zope.app.locales package make no sense anymore as it's very hard
to maintain them and it just wrong (to me at least) to have a separate
centralized translations package for
2009/2/10 Stephan Richter srich...@cosmos.phy.tufts.edu:
On Monday 09 February 2009, Dan Korostelev wrote:
Nowadays, when we have a fully egg-based setup, the translations in
the zope.app.locales package make no sense anymore as it's very hard
to maintain them and it just wrong (to me at
Hello Dan,
In short, a good translation is consistent.
That means the same sentences are translated to the same foreign
sentence. A so-called translation memory is used for that.
Also terms (specific words or expressions of the domain) are
translated to the same foreign term.
I think that's the
11 matches
Mail list logo
