[dev] Re: [l10n-dev] Re: [dev] Spanish NL Community requests for funding help on acquiring a local build box
Hi, not exactly on topic, but ... Santiago Bosio schrieb: As I said, we have been doing our own builds, patching the translations with the latest snapshot from Pootle, converted to OOo SDF format using po2oo, and gsichecking the resulting file. All of it can be done automatically, but I see two problems to solve for the as early as possible scenario: 2. Weekly devel builds should be done with the complete set of language packs, and not only a few of them as it is done currently (I think they are FR, DE, IT, JA, pt-BR, etc.) as it will give us the opportunity to check our advance (provided that we have early the strings to translate on Pootle as I said before). Unfortunately even the named languages have no chance to check their translations in an early stage. The language packs do *not* contain current translations. We have the same workflow as all other pootle based localizations: we see the finalization result in the product only after cws integration. The langpacks are only helpful to attract more people for general testing - but are a pain if someone is going to test localization. Regards, André - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] testing fix of issue 109146
Greetings,
In a comment to his change fixing issue 109146
http://www.openoffice.org/issues/show_bug.cgi?id=109146,
Stephan Bergmann commented
(but I must confess I have no idea how to trigger the code in
a running OOo, to verify that the assertion no longer wrongly
fires)
As it happens, my combination of compiler and configuration
options and I know no what else result in literal character
strings being stored at addresses according to where the string
is first encountered in the file. Within DEV300_m71, I imported
inettype.cxx after S.B.'s subsequent change ( the relevant code
reads ...
#if defined DBG_UTIL
for (sal_Size i = 0; i nSize - 1; ++i)
DBG_ASSERT(
rtl_str_compare(
pMap[i].m_pTypeName, pMap[i + 1].m_pTypeName) 0,
seekEntry(): Bad map);
#endif
), and the assertion did not fire. I verified the descending
addresses of m_pTypeName with a breakpoint at inettype.cxx:810,
and saw ...
(gdb) p pMap[61]
$1 = {m_pTypeName = 0xb754d6bd tiff, m_eTypeID = CONTENT_TYPE_IMAGE_TIFF,
m_pExtension = 0xb754d6bc }
(gdb) p pMap[62]
$2 = {m_pTypeName = 0xb754d54f txt, m_eTypeID = CONTENT_TYPE_TEXT_PLAIN,
m_pExtension = 0xb754d6bc }
Just for good measure, the following code does (rightly!) make
the assertion fire.
int tje_20100316() {
//
// Make assertion in seekEntry fire for bad sequence in the
// array to be searched.
//
MediaTypeEntry const mteBad[] =
{
{ txt, CONTENT_TYPE_TEXT_PLAIN, },
{ tiff, CONTENT_TYPE_IMAGE_TIFF, },
};
UniStringextn = UniString::CreateFromAscii( txt );
MediaTypeEntry const *pEntry =
seekEntry( extn, mteBad, sizeof( mteBad ) / sizeof( mteBad[ 0 ] ) );
return 0;
} // tje_20100316
If any of this information is worth recording in the issue, I can
do that.
Hope this helps.
Terry.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] testing fix of issue 109146
On 03/16/10 15:13, Terrence Enger wrote: In a comment to his change fixing issue 109146 http://www.openoffice.org/issues/show_bug.cgi?id=109146, Stephan Bergmann commented (but I must confess I have no idea how to trigger the code in a running OOo, to verify that the assertion no longer wrongly fires) As it happens, my combination of compiler and configuration options and I know no what else result in literal character strings being stored at addresses according to where the string is first encountered in the file. Within DEV300_m71, I imported inettype.cxx after S.B.'s subsequent change ( the relevant code reads ... [...] If any of this information is worth recording in the issue, I can do that. Terry, If you like, you can add the information (or a link to it at http://www.openoffice.org/servlets/ReadMsg?list=devmsgNo=26782) to that issue and set it to verified. That would help a lot. Thanks, -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] testing fix of issue 109146
On Tue, 2010-03-16 at 15:23 +0100, Stephan Bergmann wrote: If you like, you can add the information (or a link to it at http://www.openoffice.org/servlets/ReadMsg?list=devmsgNo=26782) to that issue and set it to verified. That would help a lot. I have added a comment with a link to the message archive. However, I cannot change the status. Cheers, Terry. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
