Clytie Siddall wrote: > On 19/07/2008, at 12:34 AM, Dwayne Bailey wrote:
>> From: João Miguel Neves <[EMAIL PROTECTED]> Date: Thu, 17 >> Jul 2008 13:18:59 +0100 >>> I'm proposing a project of a web interface for gettext-lint tools >>> (what I use for automated QA of the Firefox L10n pt-PT). >> I received this email from João and said that I would post it here >> [on the Pootle list] for further discussion. > This almost looks like an extension of the pofilter checking > functions already available in Pootle. Do we really need a separate > tool for these tasks? It would seem to me that some of the items in gettext-lint does indeed overlap with the Toolkit checking tools, but my take on this is this: there must be many different checking tools out there that people use or prefer to use for whatever reasons -- perhaps they're just used to using a certain set of tools and see no reason to move to another set. Well, just imagine how great it would be if these people could continue to use their preferred checking tools even though they're using Pootle. In fact, if there could be a function in Pootle to export its PO files along with URLs to the items in Pootle, then anyone can use his own checking tools online or offline, and still do the updates in the Pootle UI because he just clicks the links in his browser, taking him directly to the item in Pootle. I'd like to comment on Joao's mail a bit, and I'd also like to propose certain methods of accomplishing this. >> This interface would allow a user to upload gettext files and get >> several classes of error reports: * Lack of punctuation, shortcuts, >> variables and other signs. This is already present in the Toolkit, but is it perhaps easier to customise the lint tools for one's own purposes? >> * Inconsistencies in translations. I don't think this is included in Pootle, although the Toolkit does have something similar. >> * Spelling errors. This would be great, although the Lint tools currently use a very primitive spell-checking engine that only works for the most basic of languages (its spelling dictionaries consist of a list of words). It would be nice if the Lint tools can use Hunspell dictionaries. >> * Disrespect of a pre-defined glossary. I think this is one of the todos in the Toolkit, but AFAIK it has not yet been implemented. Glossary QC is part of many CAT tools, and would certainly be a nice thing to have, although it can get complicated. BTW, there is an error in the Lint readme -- it describes PoFileGlossary as something that creates a glossary, not as something that checks against a glossary. And I can't figure out what the glossary format is. >> Two use cases of the project would be pootle integration: 1) The >> report would have a direct link to the translation in each error so >> it would be easy to do the correction. Yes, this is a great idea, except for one small thing... the strings and/or their locations are not referenced in the Pootle page URLs. A page URL in Pootle contains a string number, and that number depends on the actual PO/POT file in Pootle. So the translator running these checks would have to be absolutely sure that his PO file has exactly the same number of strings as the one in Pootle, otherwise the URLs won't work. I can see two possible ways around this: 1. Pootle can be redesigned to accept URLs that contain the file names and message locations. When a Pootle server gets such a URL, it treats the URL as a search, and redirects the user to the result URL. There should be a way to handle "searches" with multiple results (in other words, when the originating report creates an ambiguous "search" URL. The advantage of the above is that anyone can zoom in on a string in Pootle even if the PO file used in creating the report is slightly different from the PO file currently in Pootle. It may also be good if Pootle can parse such URLs with the source text instead of the location comments (useful if the PO file is very simple and contains no locations, or if the source texts are all very short and the report generator prefers not to rely on locations). 2. When exporting PO files from Pootle, Pootle can put the URL of each string into the string's comment, in a format which can be parsed by another tool when it wants to create a web page report. The disadvantage of the above is that users running a report would have to first download the enriched PO file from Pootle, but on the other hand it has the advantage of forcing users to interact more closely with Pootle and ensuring that users don't run checks on old files that have already been fixed in Pootle. >> 2) A pootle server would >> have a configuration for this web interface, and a user could just >> push a button and would get redirected to the web interface with a >> report on the translation. I think being able to see a one-page report of errors instead of having to visit them individually, can be a great feature in Pootle. But I think these two use cases can be (and IMO should be) implemented separately. It would be nice if anyone from outside Pootle can generate a report that is capable of linking into Pootle, without the report generator having any kind of relationship with that Pootle server. >> The project will be done as part of the gettext-lint tools, >> Mozilla-PT group and Ubuntu's pt-PT LocoTeam. This is unfortunate -- if the developers will make no changes to Pootle itself, it means they would have to find a way to map their PO files with the PO files on a Pootle server, to ensure that URLs actually work. But I'm not a Pootle developer and perhaps there is a way to do it. Will this be forwarded to the Pootle devs? Samuel -- Samuel Murray [EMAIL PROTECTED] Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
