To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=89965
------- Additional comments from [EMAIL PROTECTED] Tue May 27 16:52:11 +0000 2008 ------- 99.97 % of all xcu's / xhp's ARE part of the l10n process ... you want invert this logic?!?!?! There is a way to exclude your special case by touch a file there what I have done. If you invert this then I don't want to be responsible that lots of strings are untranslated which the l10n QA find out 3 days before the planed release date because developers forgot to *actively* mark this file for localization ..... There is a lot mess around the extensions so why not add an example? I am already tired to fix all the xhp's / xcu's of various extensions as of wrong languages , identically identifiers , unwell formed xml code etc etc I guess the best solution is to break the build if there is something wrong in those files. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
