Hi,

thanks to all who worked on these issues. They aren't on target 3.1 anymore.

Thorsten


Thorsten Ziehm wrote:
Hi,

I want to clean up the issues for OOo 3.1. And there are still 16 issues
open for OOo 3.1 which are lying at the owner 'iss...@l10n'. Who is
responsible for the owner and who will manage the issues?

I added the list of issues at the end. The issues are for different
languages and they are for different areas. So who take care for the
issues or who will take care for all issues on this owner?

Most of the issues should be set to another target. Perhaps others can
be closed.

Here are the list of open issues with target 3.1 :

10726   DEFECT  P3 Greek characters are shown as ? character
80804 DEFECT P3 [NL] Missing translation Writer/Calc Extra > Aanpassen > Toe
80825     DEFECT     P3 NL: Duplicate Mnemonics in past-special dialog
84619     DEFECT     P3 PL: missing translation
91971     DEFECT     P3 Wrong entry for writer ui: Bibliogaphieeintrag
93316 DEFECT P3 superfluous characters (\r) in German extension manager mess
95396     DEFECT     P3 TOC is different between English and localized OLHs
95716     DEFECT     P3 Typo in a tag
96737 DEFECT P3 small typo in UI. (or not ?) officecfg / registry / data / o
97561     DEFECT     P3 Errors in original sourcetext (IMPRESS)
20521     ENHANC     P3 Consistent spelling mistake
11977 FEATUR P3 日本語で書いて&#12
86709     PATCH     P3 Translation Error in Calc
86713     PATCH     P3 Translation Error in Calc
86714     PATCH     P3 function prueba.t
85654     DEFECT     P5 [IT] Text too long in dialog (master password)

Please help checking the issues and set the issues to a correct owner and to a suitable target.

Thanks,
  Thorsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to