Clytie Siddall kirjutas: > Hi everyone :) > > On 30/09/2007, at 7:48 PM, Ain Vagula wrote: > >> Kazunari Hirano kirjutas: >>> Hi Ain, >>> >>> This list is great! :) >>> http://qa.openoffice.org/issues/show_bug.cgi?id=27685 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=42150 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=42158 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=53328 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=54446 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=54494 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=54559 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=58486 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=59796 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=62912 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=63832 >>> http://qa.openoffice.org/issues/show_bug.cgi?id=73297 >>> http://www.openoffice.org/issues/show_bug.cgi?id=82086 >>> http://www.openoffice.org/issues/show_bug.cgi?id=82087 >>> >>> Thanks, >>> khirano >>> >> >> This is only my list, I haven't filed text-not-fitting issues, also >> issues about ordering of dialog controls and strings - like "[x] of >> [y]", or "by [z] something". The idea was to collect such issues from >> other localization teams and somehow mark them to keep an eye at their >> progress and avoid duplicates. > > I have reported a lot of original-string errors (typos, broken strings, > broken placeholders etc.), but then I am told I have to report each one > against "the module concerned". Since it is very difficult to tell, from > the SDF file, which module is concerned (unless the reference is obvious > like "calc"), I don't know what to do with all these errors now. > > We do need to make it easier for translators to report problems with the > original strings. The strings themselves are not yet of a high standard, > so we need all the input we can get. >
Right, IZ has feature 'keyword', these keywords are predefined words making easier to outline and collect issues. I think, we need one or two keywords for string quality issues and for overall issues which affect localized interface. Making reporting easier cannot be done in such way because IssueZilla is 'as is'. (I dont say it is bad.) Anyways, using keyword helps to find already reported issues. Collecting and reporting string issues may be a task for leads of translation team when all members are not able to do it. ain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
