Hi Aiet, Sorry for the late entry into this discussion. As another Pootle developers I guess I should have my say also.
> > - I don't know much about the architecture of your glossary tool. It > > would be nice to find a way to integrate them that is simple. Could you > > describe the architecture (language, database etc), requirements, and > > basic 'how-it-works'? [snip] The feature set for a glossary tool and a translation tool start to look very similar. I would love to see us being able to integrate the two. > If the tool was to be integrated in another product, it would be > better to use a real database rather than XML files and have it > convert to and from various formats. If the product to be integrated > in Pootle, than I guess it should be ported to python (correct me if I > am wrong). Well Pootle uses PO files and no database. Well not quite true we use Lucene to index the data. And would probably look at that for doing the TM component. I think there would be real benefit in integrating the two. But it might be easier to allow the two to talk to each other then to rewrite it. Although doing the later might make maintenance easier. > > - Translation Memory is also important. It's not neccessarily easy to > > just pull the translation memory out of other programs. I have my own > > ideas about how to do this. > > I agree. And it will not be easy to integrate in an online tool. But > as soon as it is done, I will probably be the first person using the > tool for great many l10 projects :-) :) Yes I see it as an important way to ensure quality and consistancy. > Do you have a rough date in mind when this should be available? Be it > a month, six months or a year? Nope, we're working on some internal items which relate more to management then the online translation component. of course that doesn't stop anyone from making th TM part work. > While the product is indeed very useful to many projects the way it is > now, I think we will have to wait for TM functionality before the tool > can be used for OOo l10n. I don't necessarily agree. If TM is important to you we could do the following. 1) Work offline as use Pootle to get and submit files 2) Maintain your own TM in your favourite offline product by downloading all the .PO files > I think it would be nice to decide which way to go now: Try to embed > the glossary management tool in Pootle soon and have the whole product > embedded to Native-Lang pages, wait for the TM functionality while > integrating the glossary management to the tool and embedding the > product as soon as TM and Glossary functions are fully integrated, or > try to embed the glossary management on NL sites first and later also > embed Pootle, as soon as it features TM functionality. I would love to see this embedded. In fact it was a desire of the Pootle team to see larger projects integrate the tool into their processes. > Right. But when talking about the glossary tool I developed, I will > put it under GPL and we can just use the code in Pootle (so it will no > longer be a third-party tool). Pootle is also released under GPL, > right? Yes > While I was not able to install the product yet (btw, are there any > instructions how it can be installed without root privileges?), Just looked seems like we can't at the moment. > would > you mind stating the features Pootle is offering at present? It would > enable us to decide whether it would be best to integrate the tool > directly or wait until some other features are added. - Manage multiple languages - Manage multiple projects (eg. OpenOffice, Mozilla, etc) - Download PO or CSV files - Download a ZIP of the project or directory - Upload files, ZIP archive - Build MO files on the fly - Allow user to view, suggest or translate a translation - Quick translate: takes you to the next fuzzy or untranslated in the directory structure. - Allow review of suggestions - Create diffs between suggestion(s) and current translation to see what changed - Assign rights to users - Search translations for a specific string - Special characters. Allows you to list accented chars for users without good keyboard setups. - About 20 checks from accelerators to variables and punctuation. You can scan through each type of error. - Initiate a project for a language from PO Templates - Update against a CVS/SVN repository, turning conflicts into suggestions - Delegate admin functions to a "language and project" lead - Create named goals for a "language and project" - Browse the tree to see completion stats at any level Some of the tasks we are working on now: - Packaging assigned work - Various stats about completion of assigned work - Commenting on errors: a commented review mode - Integrating corrections - Refining goal setting So any other Python developers out there care to join us? -- Dwayne Bailey <[EMAIL PROTECTED]> Translate.org.za +27-12-460-1095 (w) +27-83-443-7114 (cell) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
