On 05/07/2006, at 3:32 AM, Brad Knowles wrote:
Ethan replied to Barry:
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
Have you gotten any love on this issue Ethan?
No love as of this writing. I'm continuing to kick the i18n ball down the field until I can do a translation myself (into gods-knows-what - I'll probably have to rely on my lovely and talented wife to give Russian/Italian a stab.)
I've got MacOS X 10.4, but I don't do any sort of translation, and I don't have the slightest clue as to how you'd go about trying to do that. I don't speak any foreign language well enough to even think about making any attempt to do so.
That said, I'd be glad to provide whatever help I can.
Sorry I haven't been able to answer this before. :(
I'm also on OSX. OK, sample translator workflow (different procdures for different projects!):
Get files: email updates, download from web, CVS or SVN.
Initiallize files with translation memory: gettext (msgmerge) or TMX, via my translation editor LocFactoryEditor , or use Pootle 
Translate files: LocFactoryEditor, BBEdit (text editor) or Pootle, depending on type and complexity of work
Check files: gettext (msgfmt), translate toolkit (pofilter) , spellchecking (aspell, CocoaAspell  and a Debian script ) again via LFE and/ or Pootle
Send in files: email, FTP, CVS or SVN
You might like to look at the Debian/Wordforge plans for a complete translation infrastructure. . I believe this is the future of i18n.
You're welcome to ask me for more details. That's the skeleton.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
 http://www.triplespin.com/en/products/locfactoryeditor.html  http://translate.sourceforge.net/wiki/pootle  http://www.barebones.com/index.shtml  http://translate.sourceforge.net/wiki/toolkit/index  http://people.ict.usc.edu/%7Eleuski/cocoaspell/home.html  svn://email@example.com/svn/d-i/trunk/scripts/l10n/  Not sure if this is documented in any one place, but check out the Pootle roadmap (http://translate.sourceforge.net/wiki/wordforge/ functional_specificaions) and threads starting in late May on translate-pootle (https://lists.sourceforge.net/lists/listinfo/ translate-pootle) and debian-i18n (http://lists.debian.org/debian- i18n/) about SoC, Wordforge and i18n infrastructure.