summaryrefslogtreecommitdiff
path: root/l10ntools/source
diff options
context:
space:
mode:
authorAndras Timar <andras.timar@collabora.com>2013-11-15 21:07:57 +0100
committerAndras Timar <andras.timar@collabora.com>2013-11-15 21:16:27 +0100
commitf64ef0b43a5cd97657cffa2cfb415d523d55095c (patch)
treee37ea179e9b3040cda21623b59f476e386118371 /l10ntools/source
parentec6d0deca7e2fcde1f461e093b51bd101fe1eba9 (diff)
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
Diffstat (limited to 'l10ntools/source')
-rw-r--r--l10ntools/source/lngmerge.cxx4
1 files changed, 2 insertions, 2 deletions
diff --git a/l10ntools/source/lngmerge.cxx b/l10ntools/source/lngmerge.cxx
index 4913bc46d700..fc8aa7b4187e 100644
--- a/l10ntools/source/lngmerge.cxx
+++ b/l10ntools/source/lngmerge.cxx
@@ -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;