Hi Thorsten, Thorsten Ziehm wrote: > Hi Sophie, > >> And I hope you would like us to work together on a solution that will >> bring more contributors to your teams. Most of them are able to test an >> English release and will understand the work needed but won't be able to >> report a bug or express them self in English, at least at the beginning. > > I agreed on all, what you wrote. We have to work together to bring more > contributors to the QA project. If they are organized in the NCL teams > or in the application teams or ... never mind .
Thanks :) > But as you also wrote, > it is important to bring them early on the developer snap shots to avoid > the work on more than 1 RC. Yes, and this process has to be work out, NLC has to call up its resources. > > One thing I take from this discussion is, that the NCL teams need a > compressed document, where they can find the features with new or > changed translation. Sorry to say, but currently I do not have an idea > how to generate such a list. Perhaps someone else has an idea. For the OLH, I can't remember who has provided xml files (allfile.tree and main_transform.xsl) that you can add in the program/help directory. That will add an extra directory in the help view called "all files for testing". The directory will show the page with the same structure as the po files (for example schart/00/00000004.xhp, which will be corresponding to #: 0000004.xhp#par_id3146883.32.help.text id in the po file). So for the help file, this will be quite straight to list the directories concerned and search in the "all files for testing". For the GUI, I don't know. Even if we could have KeyID builds, it won't be easy to find the strings. > > To discuss the needs of the NLC teams (for doing QA) is a good side > track on OOoCon. Are you in Barcelona? Yes, as Charles says :) Kind regards Sophie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
