Kaydet (Commit) f64ef0b4 authored tarafından Andras Timar's avatar Andras Timar

qtz handling in ulfex

If we don't want to use qtz codes in .ulf files, then why
do we write out qtz language with en-US content?
In fact this patch would not be necessary, if I didn't find
a build breaker bug, somehow sNewText was empty for certain
strings, and the sNewText.copy(sNewText.indexOf('|') + 2)
failed.

Change-Id: Idf377e61391eb08ecb692a7c404d190659b97575
üst ec6d0dec
......@@ -244,7 +244,7 @@ sal_Bool LngParser::Merge(
OString sNewText;
pEntrys->GetText( sNewText, STRING_TYP_TEXT, sLang, sal_True );
if( sLang == "qtz" )
sNewText = sNewText.copy(sNewText.indexOf('|') + 2);
continue;
if ( !sNewText.isEmpty()) {
OString *pLine = (*pLines)[ nPos ];
......@@ -282,7 +282,7 @@ sal_Bool LngParser::Merge(
OString sNewText;
pEntrys->GetText( sNewText, STRING_TYP_TEXT, sCur, sal_True );
if( sCur == "qtz" )
sNewText = sNewText.copy(sNewText.indexOf('|') + 2);
continue;
if ( !sNewText.isEmpty() && sCur != "x-comment")
{
OString sLine;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment