trans September 2008

trans@lists.fedoraproject.org

32 participants
50 discussions

Translation Schedule F10 and beyond
by John Poelstra 22 Sep '08

22 Sep '08

Hello everyone, There have been some recent discussions on fedora-devel-list about some of the scheduled dates for translation and needing to refine them a bit. We probably won't be able to adjust the general Fedora 10 milestones at this point, but we can add Translation specific tasks and deadlines so that other parts of Fedora have a better understanding of all the great work your team does! In a separate email in the future we can also start defining a Fedora 11 schedule that will work better for you. As a starting point I've stubbed out a schedule using the general Fedora milestones. http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html Please let me know which additional tasks you would like to include on the Translation schedule. To accurately reflect each task (and so that we can automatically generate a schedule in the future) please tell me: a) task name b) when the task starts c) how many work days the task takes d) other task(s) that must finish prior to this task starting(dependencies) Once we have all of the tasks defined that you would like I will add the remaining reports for your team and then they will appear in the title bar like the other teams: http://poelstra.fedorapeople.org/schedules/f-10/f-10-all-tasks.html Art, Docs, etc. If there are other ways I can help please let me know. John p.s. If you're interested in how TaskJuggler works you can download the source and build schedules yourself following these directions: http://poelstra.fedorapeople.org/schedules/f-10/source/readme

2 4

Moving TQSG to FedoraHosted
by Fabian Affolter 22 Sep '08

22 Sep '08

Hi all, Paul mentioned [1] that it would be a good idea to move L10n relevant documents, like TQSG, from Docs CVS to FedoraHosted. What do you think about that step? Kind regards, Fabian [1] https://bugzilla.redhat.com/show_bug.cgi?id=461762 -- Fingerprint: 2F6C 930F D3C4 7E38 6AFA 4EB4 E23C D2DD 36A4 397F Fedora always leads and never follows.

4 3

[Bug 139069] Incorrect file reference in dhcpv6 description
by Red Hat Bugzilla 21 Sep '08

21 Sep '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=139069 Göran Uddeborg <goeran(a)uddeborg.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE --- Comment #8 from Göran Uddeborg <goeran(a)uddeborg.se> 2008-09-21 12:55:12 EDT --- The description for 1.0.14-1.fc9 doesn't have this problem any more. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

Transifex and Damn Lies
by Noriko Mizumoto 19 Sep '08

19 Sep '08

Hi translators! We have been experiencing some maintenance on TX and DL. No need to mention as everyone knows, tremendous effort is on it's way. The question may come up in mind, 'then what to do? I can't contribute till then?' The answer is 'yes, you can.' If you encounter any error in TX, please submit your translated file via bugzilla just like filing a bug. cheers noriko

7 20

trnaslation-filter
by Marek Mahut 18 Sep '08

18 Sep '08

Interesting project: https://fedorahosted.org/translation-filter -- Marek Mahut https://fedoraproject.org/wiki/SIGs/Astronomy/ Fedora Project http://www.jamendo.com/

1 0

[Bug 452488] New: Typo
by Red Hat Bugzilla 17 Sep '08

17 Sep '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=452488 Summary: Typo Product: Fedora Localization Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: Other language AssignedTo: dimitris(a)glezos.com ReportedBy: mgiri(a)redhat.com QAContact: aalam(a)redhat.com CC: fedora-trans-list(a)redhat.com Description of problem: Typo Version-Release number of selected component (if applicable): fedora-9 How reproducible: Always Steps to Reproduce: 1.Go to the po file of policycoreutils.HEAD ,msgid:362 2.Check the spell of 'Enforcment'in that string 3. Actual results: It is 'Enforcment' Expected results: It should be 'Enforcement' Additional info: -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 1

FLP Meeting 2008-09-16 Summary
by Fabian Affolter 17 Sep '08

17 Sep '08

== Summary == FLP move the translation freeze from 21/10 to 14/10. Schedule: http://fedoraproject.org/wiki/Releases/10/Schedule TODO: Get a reply from RelEng, update Schedule, mail -trans-list and -devel-list (glezos, noriko) We need to make sure the packages which are shipped, Fedora is upstream for, and FLP translate are re-packaged between the T Deadline and the Development Freeze. TODO: Ask on -trans-list and -infrastructure-list for people to hack a script for checking re-packaging. The documentation and communication with 'devel' have to increase. More emails to -devel-list and -devel-announce TODO: Send an email to releng reminding them to have a section for L10n in their mails to -devel-announce. Specifically, in the one announcing that in X days the development freeze will happen. The maintenance of our L10n infrastructure has issues. I'm doing my best with my experience (developer, not administrator) and time to manage it We've repeatedly asked for folks interested in it to help out with the administration. The call is still open. The Fedora language teams are of course made of both internal and external translators. Working together gets maximum benefits from both groups. TODO: Lead the effort in doubling the number of languages Fedora is announced in. Help people with anything they might need. (noriko, glezos) If I missed some point, feel free to add those. -- Fingerprint: 2F6C 930F D3C4 7E38 6AFA 4EB4 E23C D2DD 36A4 397F Fedora always leads and never follows.

1 0

FLP Meeting 2008-09-16 IRC Log
by Dimitris Glezos 17 Sep '08

17 Sep '08

* glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Init <glezos> hey all <glezos> It's the FLP meeting, live from selected locations around the world! <ankit> hi glezos <glezos> Good day, afternoon and evening, wherever you are. :) <glezos> <rollcall> * cassmodiah has quit (Read error: 104 (Connection reset by peer)) * marek Marek Mahut (sk) <runa_b> Runa Bhattacharjee (bn_IN) <ankit> Ankit (gu) <fabian_a> Fabian Affolter (de) <Bouska1> Pablo Martin-Gomez (fr) <glezos> Dimitris Glezos (el) <Rasther> DiegoZacarao (pt_BR) * noriko (n=noriko(a)d220-239-22-97.rdl17.qld.optusnet.com.au) has joined #fedora-meeting <noriko> Noriko Mizumoto (ja) <glezos> right on. * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Update on previous' meeting action items <glezos> Last meeting's minutes: https://www.redhat.com/archives/fedora-trans-list/2008-July/msg00080.html <glezos> (thanks Noriko) <noriko> :) <glezos> Who'd like to volunteer to prepare this meeting's minutes? <fabian_a> i will do it <glezos> I'll mark all action items in the log. :) <glezos> fabian_a: great, thanks. <glezos> So, on the past action items/summary <glezos> Freeze and Deadlines: * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Update on previous' meeting action items -- Freezes * LetoTo2 has quit (Remote closed the connection) * LetoTo1 (n=paul(a)76-10-173-74.dsl.teksavvy.com) has joined #fedora-meeting <glezos> The FLSCo discussed about changing the Translation Deadline to one week earlier, to give enough time to packagers to repackage their translations <glezos> The vote passed, and I've sent an email to RelEng. Waiting for their answer. <glezos> f13: ping, if around: Should we go on with the Schedule updating, now that RelEng hasn't raised any concerns? <glezos> Schedule: http://fedoraproject.org/wiki/Releases/10/Schedule -- We'll move it from 21/10 to 14/10. Still enough time for plenty translations. <glezos> I'd like to thank everyone on FLSCo for quickly giving their feedback, and helping getting this issue close to resolving. <glezos> This is exactly why we have created the group, to have an official stamp of approval for these kinds of decisions <glezos> noriko was the main player here who pinged me and sees the issue to completion. Thanks. <glezos> TODO: Get a reply from RelEng, update Schedule, mail -trans-list and -devel-list (glezos, noriko) <glezos> comments? <ankit> thx guys for sorting out the issue! <runa_b> glezos: should we go ahead with 14th as the target or wait until rel-eng reverts? <runa_b> i mean is there any chance of change in the schedule.. based upon rel-eng's feedback <glezos> runa_b: The translation deadline is FLSCo's call (it doesn't affect the releng procedure), and I think it's safe to assume that we'll move it in the following days. <runa_b> glezos: right. as long as the packages are rebuilt once again post 14th.. things look all set <noriko> actually it would be good for packagers too, allowing more time to include translation. <glezos> right. <noriko> I am happy to see this happened, thank you all! <glezos> One of the things we'd like to have is someone write a Python script that queries Koji and notifies for any core packages that haven't been rebuild. <glezos> Volunteer Python hackers are welcome to play with it ($me discretely pointing to fabian_a) <noriko> glezos: sounds good idea, but could you please explain me what exactly happen or the benefit of it? <Rasther> this would be great <runa_b> glezos: good one.. this would be cool <glezos> noriko: We need to make sure the packages which are shipped, Fedora is upstream for, and FLP translate are re-packaged between the T Deadline and the Development Freeze. A script could take care of that. <glezos> TODO: Ask on -trans-list and -infrastructure-list for people to hack a script for checking re-packaging. * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Update on previous' meeting action items -- FUDCon Brno <noriko> glezos: yp! that is what we need!! Rasther rayvd rdieter ReneP ricky rsc runa_b rwmjones <glezos> glezos, Rasther and Cmpahar were there. Quite some Transifex hacking, lots of input from folks. <glezos> Event reports at https://fedoraproject.org/wiki/FUDCon/FUDConBrno2008#Event_Reports <f13> glezos: please do <glezos> f13: thank you <zebob> thx ! <glezos> I had a few discussions with Fedora and RH developers who receive translations through Transifex. They seem very satisfied with the fact that they spend much less time with translations now. <glezos> Some feedback I got suggested to increase the documentation and communication with them for what we need. More emails to -devel-list and -devel-announce <glezos> TODO: Send an email to releng reminding them to have a section for L10n in their mails to -devel-announce. Specifically, in the one announcing that in X days the development freeze will happen. * sharkcz has quit ("Ukončuji") * Sonar_Guy (n=Who_Know@fedora/sonarguy) has joined #fedora-meeting <glezos> The Transifex speech went pretty well. It seems that a lot of folks, downstream and upstream, Fedora developers and independent ones, are looking forward to a common installation on a central location (eg. transifex.net/com) for an upstream translation community to be formed there. <marek> glezos: I had, unfortunately, bad reports about transifex server stability from community :( <marek> they don't want to use it and prefers to send me the po files directly by mail :( <glezos> marek: yes, the maintenance of our L10n infrastructure has issues. I'm doing my best with my experience (developer, not administrator) and time to manage it <marek> I'll try to reserve a time to help with that <glezos> we've repeatedly asked for folks interested in it to help out with the administration. The call is still open. <marek> glezos: do we know what's the root cause of the slowness? <marek> application or misconfiguration or anything else? <glezos> Also, I think many people also have raised the opinion that having a RH person also accountable for these could greatly improve our productivity. <marek> indeed, but you know... it's not a Red Hat product :) <glezos> marek: Tx is OK, Damned Lies is slow. One reason is because the DB is in SQLite and gets quite big sometimes and needs cleanup. Also DL needs updating to newer versions (trunk) <glezos> Transifex (/submit) is always responsive, AFAIK. Please correct me if I'm wrong. <marek> yup that's true <noriko> so the bottleneck is DL.... <glezos> marek: Maybe you could install the flpweb module (/cvs/l10n), get it running, and report back. Then we could see if we could give you access to app1 & 2 where DL runs. <marek> looks so, because the statistics pages takes about 25 seconds to load <marek> others are fine <glezos> noriko: yes. DL's upstream has decided not to develop much code, because they are merging their efforts in Transifex <marek> which is good :) * rwmjones_ (n=rwmjones(a)87.127.66.208) has joined #fedora-meeting <glezos> so maybe folks wanting to help make things better could work on improving Transifex's low-level bits (load-balance support for example). <glezos> FWIW, I'm actively working on adding statistics support in Tx. The plan is described here: http://transifex.org/wiki/Development/Statistics <glezos> So, the statistics for F10 were fixed (thanks Piotr for keeping the conf up2date) <glezos> already late, let's get moving * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- F10 schedule: Freezes and deadlines <glezos> we've covered this already, cool * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- L10n tool updates (New modules, features, FUDCon Brno, [RHT/I18n ideas]) <glezos> New modules on Transifex since last meeting: Folks can scroll back in the -trans-list archive for announcments on this. We encourage developers to announce (and blog) when we add their module. * Stalwart (n=stalwart(a)ip-10.154.Home-Lan.fastnet.lv) has joined #fedora-meeting <glezos> Most notable recent addition is PulseAudio. <glezos> (yeehaa!) <runa_b> :) <glezos> It's pretty exciting seeing upstream projects trusting the Fedora community as an entry point to their code. <glezos> Good work guys. :) <noriko> wow * rdieter has quit (Remote closed the connection) <Rasther> cool * ltinkl (n=ltinkl(a)194.212.22.14) has left #fedora-meeting ("Konversation terminated!") <glezos> RHT I18n office has sent an email to -infrastructure-list for some plans they have for building a new tool around translations. <glezos> You can see the discussion here: http://markmail.org/message/vigf324ce2rbk6n6 <glezos> I'll let asgeirf_ communicate with -trans-list of any possible benefits for the project from the tool. * giallu (n=giallu@fedora/giallu) has joined #fedora-meeting * poelcat just saw mention of schedule... and is behind on replying to email :( <glezos> poelcat: no worries. I'll update the Schedule and let you know of the new date. <poelcat> glezos: oh, i was speaking to fixing up the taskjuggler schedule <glezos> poelcat: OK. I can think of a small fix: The aggregated view shows translation dates from both software and documentation, but IIRC they have similar descriptions. We could add something like 'PO files due **for Docs**' to distinguish them <glezos> TODO: send poelcat updated versions of the schedule, and specific requests for text changes in the schedule's items. <glezos> TODO from before: let glezos know if there's anything I need to start hacking on our Infrastructure (marek) :-) * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Update on Fedora 10 Docs shipped in internally-supported languages <glezos> I've asked ankit and manuel (L10n team leads in RH) for input whether we could get relnotes into more languages from internal translators in RH <glezos> By announcing Fedora in more languages we can increase our coverage, local media will pick up the news/write an article more easily etc. <glezos> Having Fedora announced in something like 30+ languages would be fantastic. <noriko> I will take a lead for languages on be half of Manuel, while ankit is taking a lead for indic languages. <glezos> noriko: awesome. Let us know of the progress! <Rasther> glezos: apparently the pt_BR team will take some contributions from there <noriko> Rasther, glezos, yes. some of translators have started their contribution. <glezos> Rasther: definitely. The Fedora language teams are of course made of both internal and external translators. Working together gets maximum benefits from both groups. <noriko> there are some translators who are not familar with the community work, so pls let me know if I can support. <glezos> TODO: Lead the effort in doubling the number of languages Fedora is announced in. Help people with anything they might need. (noriko, glezos) <Rasther> glezos, noriko: Glaucia Cintra sent a email asking some doc modules to work on * spot has quit (Remote closed the connection) * spot (i=spot(a)beer.tclug.org) has joined #fedora-meeting <glezos> I suspect that seeing this effort into completion is going to be a big success, both for Fedora and Red Hat. * EvilBob (n=bjensen(a)fedora/pdpc.sustaining.BobJensen) has joined #Fedora-Meeting <noriko> Rasther: noted, I will contact her today to help, thanks! * huffd has quit (Remote closed the connection) * huffd (n=dhuff@nat/redhat/x-eb03217795baf050) has joined #fedora-meeting * sm|CPU has quit (Read error: 104 (Connection reset by peer)) <glezos> The most important bit here is probably to help internal folks with what they might need to work with the existing Fedora teams. * sm|CPU (i=sankarsh(a)72.20.2.58) has joined #fedora-meeting <glezos> Let's make sure this synergy will happen, and it will be done in the most efficient way. <glezos> noriko: let me know if you need anything. <Rasther> noriko: ok, thanks <glezos> Opening up floor for general discussion. * glezos has changed the topic to: /topic Fedora Localization Group meeting -- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Open floor / AOB (any other business) * fab__ has quit ("Leaving") * runa_b has one * than_home (n=than(a)p5797C6CA.dip.t-dialin.net) has joined #fedora-meeting <glezos> runa_b: fire aqway <glezos> away. * runa_b is taking over the the Translation beat for the FWN from marek from this week. <noriko> thank you so much runa_b !! <glezos> oh yes. runa_b, that'd be great. <runa_b> maybe i'll put togehter a L10n news page linked from the L10n page..so that everyone can put in there news bits too <glezos> runa_b, do you have any ideas on how we could collaboratively chip in for that effort? <glezos> oh, just answered it. :) <runa_b> so that they can make sure somethign important is not missed :) <runa_b> would a weekly reminder for news help? <runa_b> on the mailing list... <glezos> runa_b: So I guess your plan is collecting news bits (bullets) during the week.. and anyone wanting to add a suggestion for inclusion, could do it by putting a bullet there? <runa_b> yup <glezos> excellent. <runa_b> especially maybe any changes to the l10n infrastructure <glezos> runa_b: will do. The weekly reminder could help IMO. Especially if it had reminders for some often-used categories of news we could add (eg. New modules on Tx, Updates from local teams, etc) <glezos> any other topic folks would like to discuss? <runa_b> glezos: cool.. thats a nice thing <Bouska1> yes, i have just a question <glezos> Bouska1: we're all ears. :) <Bouska1> just to know approximatly when Tx will be able to send mails when a new translation is there, because we, french team, we are quite depending on this because we use a ML for translating <glezos> Bouska1: Good Q. This is a Tx related issue, so I think opening a ticket on transifex.org could get someone to code this. <glezos> Then, it's up to Fedora Infra to update our Tx installation with the new release containing this feature. <Bouska1> ok, i put this on my todo list <Bouska1> an other question about Tx ... <glezos> Bouska1: To give you an estimation, I think 2 months is a good estimation. <glezos> Bouska1: FWIW, we have a channel that a lot of transifex hackers hang around -- #transifex <glezos> If it's not a question for the Fedora L10n Steering Committee, I think questions have a higher chance of getting a good response/feedback there. <glezos> But please, feel free to ask anything you need. <Bouska1> glezos: ok, i will go there when i have time * ankit got to go now... thx everyone! * ankit has quit ("Off for the day !!!") <glezos> Bouska1: ok, thanks. <glezos> so, it's getting late. <glezos> If there's nothing else, closing in 30 <glezos> </meeting> <glezos> thanks everyone. <Rasther> thanks... and good night <runa_b> Thanks a lot everyone.. its good to meet up <fabian_a> glezos: thanks <Bouska1> good night all :-)

1 0

FLP Meeting Reminder 2008-09-16 20:00 UTC
by Dimitris Glezos 16 Sep '08

16 Sep '08

Kindly reminding everyone (and especially FLSCo) that tonight we're meeting in #fedora-meeting for about an hour. To see what that time is in your local timezone use [1], or for more command-line tools refer to [2]. The meeting's agenda is at: http://fedoraproject.org/wiki/L10N/Meetings#agenda -d [1]: http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=16&year=20… [2]: http://fedoraproject.org/wiki/Infrastructure/UTCHowto -- Dimitris Glezos Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) -- -- Dimitris Glezos Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) --

1 0

Re: Planning a future L10N infrastructure (including Fedora)
by Asgeir Frimannsson 16 Sep '08

16 Sep '08

On Mon, Sep 15, 2008 at 10:48 PM, "Sankarshan (সঙ্কর্ষণ)" <sankarshan.mukhopadhyay(a)gmail.com> wrote: > > Asgeir Frimannsson wrote: > > > Some of the immediate needs that could be addressed within the existing > > framework (some of which are on the Transifex roadmap) are: > > - Consolidation of Damned Lies and Transifex, allowing retrieving and > > submitting translations through the same interface > > - Allowing retrieving and submitting multiple-files at once (e.g. for > > translating a publican document with many PO files) > > - Simple workflow on top of Transifex (porting features from Vertimus) > > - Better usability and easier user registration process (Fedora specific) > > Which ones are not on Tx roadmap ? And, how are those elements proposed > to be met ? Background: http://groups.google.com/group/transifex- devel/browse_thread/thread/a637310e8ff63555 http://transifex.org/wiki/Development/Roadmap http://transifex.org/roadmap Dimitris is a better person to answer this, but I believe we already have basic statistics support finished in Transifex upstream. Also, I know Stéphane Raimbault is involved in integrating the concepts found in Vertimus into Transifex. What the future regarding integration of Damned Lies concepts such as Teams and Releases is, I am not sure. > > Looking at the bigger picture, some of the core requirements we have identified > > for Red Hat and community L10N going forward are: > > - Customizable Translation Workflows and integration with e.g. Content > > Authoring Workflows > > - Infrastructure easily adaptable to support new File formats and project > > types (e.g. OpenOffice formats, CMS formats, DTP formats, Wiki, Dita, Java > > formats), rather than relying on 'upstream' projects to fit a certain L10N > > infrastructure. > > - Managing the life-cycle of a translation project across releases and > > iterations > > - Translation Reuse and Terminology Management across projects and iterations > > - Job management, scoping, tracking and resourcing > > - Managing and/or Tracking upstream translation projects, pushing changes back > > upstream. > > Since Tx is gaining traction with other communities as well, is it > prudent to open the net wider and ask about the requirements from such > communities ? Yes. I would however add that this project is not directly linked with Tx at this point. Dimitris has done a great job in networking with other communities, and have a plan for Tx that goes way beyond Fedora. > > These requirements require a system where the translation lifecycle would be > > managed within 'Translation Repositories' (similar to e.g. Pootle or Launchpad > > Translations), rather than directly through e.g. upstream version control > > systems. With a repository-based approach, we would be able to track and > > manage changes to a project on a translation unit level, and manage e.g. > > translation reuse and terminology within and across projects. We could still > > retain a link with upstream repositories (like with Transifex/Damned Lies). > > However, this would not be the 'core datamodel', but on a different layer > > through plug-ins. This link to external repositories could also go beyond > > traditional version control systems, communicating with external sources like > > wikis and CMSs. > > Does Transifex allow such a set of 'plug-ins' ? If yes, how would one go > about integrating them within the plans of Transifex ? If not, how does > the integration happen ? The existing Transifex handles very different concepts than what is described here, and writing this on top of transifex would be hard. Take for example the 'submission' page, this page is centered around submitting a file to a repository (or to bugzilla, email as a result of Christos' SoC work). In a Repository-model, the 'submit' action would be more about updating the internal state of a project within a repository. To achieve the same 'workflow' as Transifex, an external plugin could then 'listen' to these changes and transparently submit changes upstream (even by interacting with Transifex?). In this sense, the project we are proposing could use the submission logic of Tx, but handle that in the background. There will be little reuse of actual code from Transifex (most of which is UI-Model interaction which is linked with file submission). It is also important to note that the internal format of the repository will not be PO, but a much richer format more similar to e.g. XLIFF, that accommodates features such as change tracking and terminology-annotations within translation units. PO would still be supported as an input format, as well as an intermediate format that is sent to translators using existing PO tools. However, in the long term, we aim to provide translators with richer tools that can make use of the additional meta-data that is part of the repository. Dimitris mentioned on IRC the other day that the concept of a Translation Repository similar to e.g. Pootle had been briefly discussed, and could be part of Transifex in the future. This is exciting news, utilizing Translate Toolkit more is something that could take Tx to the next level quickly. I think Transifex with its existing Roadmap serves a very useful purpose, and we are not trying to 'hijack' that project in any way. In fact, I am also pushing towards putting more resources into transifex development (read between the lines whatever you want here). What we are about to develop is a new way of doing localisation repositories and workflow, more similar to what happens in many commercial tools than what we see in open source communities. I feel a bit 'uneasy' about pushing that onto the Tx roadmap at this stage, and also uneasy about developing such a 'workflow system' in Turbogears. > > We have evaluated a number of existing open source L10N frameworks and > > systems, but haven't found any (yet) that stands out or satisfies our needs or > > requirements as a development platform. Technology-wise, we are aiming to > > develop a Java-based(!) system, using technology such as JBoss Seam, > > Hibernate, jBPM and RichFaces. A java based platform will enable us to make > > best use of internal expertise in these technologies, as well as making use of > > technology we are developing (as open source) through collaboration with > > partners in the L10N industry. > > Can the results of the evaluation be shared ? So the alternatives would be Pootle (Translate Toolkit), and Transifex (Tx+DL+Vertimus), pootle clearly being the more mature from a resource- management perspective. Pootle works with PO, XLIFF and many other formats. Still, it is very limited in its use of e.g. workflow support and translation memory management. One of the main architectural limitations of Translate Toolkit is it's inheritance hierarchy, where all resource-formats (e.g. PO, Properties, XLIFF, TMX) inherit from a base resource class. A 'pivot' format (similar to e.g. XLIFF) with converters to and from the native format is what we're looking for. Nevertheless, Translate Toolkit (and even Damned Lies) has a lot of knowledge vested in it in how to handle specific project types (intltool, gnome-doc-utils, firefox, openoffice). This is reusable across solutions. Feature-wise, it is much more interesting to compare with e.g. Idiom WorldServer and Lionbridge Freeway, which are commercial solutions in the L10N space. cheers, asgeir

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans September 2008