Hi, I took the liberty of changing the topic in order to fork this trhead.
2009/10/8 Joshua A. Andler <scislac@...5...>
Lucas,
I agree that it would be helpful for it to be as final as possible. Being a native English speaker, I assumed that having knowledge in advance would be advantageous to get most of the work out of the way. Apparently the translation process is more specific and intricate than I had assumed. Lucas, can you suggest what would be most helpful to translators? Not saying anything until it's finalized?
Stating what is
completely finalized?
This last option would be great. The main problem with translating wiki texts is that it's difficult to see what has changed from one version of the text to another. I know there's an option to see the changes in a page, that's part of the wiki philosophy, but when using "third party" translation tools that becomes almost useless. For example, I use a tool called "OmegaT" to translate web pages. The workflow is as follows (for almost all types of texts): 1- download the html page 2- segment the file (the software separates the text in "translation units"; phrases, titles, etc.) 3- translate all the segments 4- put the file back together in the target language 5- upload the translated file
Now imagine the original file changes, the workflow is almost the same: 1- download the html page 2- segment the file (this separates the text in "translation units"; phrases, titles, etc.) 3- the software detects the segments that are not the same and marks them as "fuzzy" (usually indicating a percentage of coincidence) 4- translate the changed and new segments 5- put the file back together in the target language
With wiki texts the worklow fails at #1. You cannot download the text to be interpreted by the software, so it all becomes a manual process (back to the ice age of comparing texts one next to the other, yuk).
I don't know a real solution yet, maybe there's space here for an open-source "Wiki Translation" project ;-) such as those discussed at http://wiki-translation.com/
Anyway, We'll do our best !!!
Cheers, Josh
On Thu, 2009-10-08 at 09:52 +0200, Lucas Vieites wrote:
Hi, I just copied the English text to the existing "es" page: http://wiki.inkscape.org/wiki/index.php/Inkscape047-PRannounce-es but I think there's parts of the text that can/should be omitted in the final press release. Also, It's very difficult to keep a translation up to date in a wiki if the original is not finished, So it would be very useful if the press release is as much finished as possible before translation begins. Are we at this point? Are major changes in the press release to be expected?
Thanks,
Lucas Vieites Blog: http://blog.codexion.com/
2009/10/8 Lucas Vieites <lucas@...162...> Hi, I'll take care of the spanish version if that's OK. -- Lucas Vieites Blog: http://blog.codexion.com/
2009/10/7 Uwe Schöler <mail@...152...> Hey all, we need help in translating the announcement for the new releasehttp://wiki.inkscape.org/wiki/index.php/AnnouncePlanning047
to different languages. It's easy with the wiki and if someone needs help with it, he or she can email me or catch me in the inkscape channel. I started the translation for Germanhttp://wiki.inkscape.org/wiki/index.php/AnnouncePlanning047_de
Sincerely, UweSch Joshua A. Andler schrieb: > Hey All, > > I forgot to post to the user and translator lists because I was too > excited. :) > > I think we closed out the last of the blocker bugs today! > > So, will people please help ensure that the release notes are up to > date? I'm headed there in just a minute to document my latest changes. >http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47
> > Regarding PR, I am going to continue with what was started here: >http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning047
> If you are an inkscape user who wants to contribute, even if you can't > program, this is the perfect way to give back to the community. Please > help us flesh this out and refine it. > > Packagers, please package up Pre3 if you have not already done so as a > practice run... and honestly, I think it would be safe to plan a release > for next week (between Monday the 5th and Friday the 9th), provided > packages are available and no new issues arise. > > Any objections to this proposed plan? Any thoughts on if releasing on a > specific day of the week will get more notice? > > Oh, and translators... please get any updates submitted asap. Thanks! > > Cheers, > Josh > > > > > > >
> Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Inkscape-translator mailing list > Inkscape-translator@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>
Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/inkscape-translator
Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Inkscape-translator
mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator