[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: kate 4.10.1 bracket completion
From:       Burkhard =?ISO-8859-1?Q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2013-04-09 19:23:06
Message-ID: 1923648.AWk0Mz6oTo () parodia
[Download RAW message or body]

Am Dienstag, 9. April 2013, 18:10:47 schrieb Dominik Haumann:
> 
> to fix bug https://bugs.kde.org/show_bug.cgi?id=241104 the built-in
> autobracket feature was removed for KDE 4.10. There are quite a lot of users
> now who complain [1] that the autobrace plugin does not match the
> auto-bracket features.
> 
> Therefore, we consider adding the feature again, i.e., reverting the commit:
> http://commits.kde.org/kate/d51d4820a854985a833f28f1facac9d9287466ab
> 
> However, for KDE 4.10 this would reintroduce several strings again. Would
> that be ok, if we commit this in this week, to have it back for KDE 4.10.3?
> The translators would have 3 weeks then. Or should we got for 4.11?
> 
Reverting the commit will readd 6 "new" translation strings (2 for 
ktexteditor_plugins.po, 2 for katepart4.po, 2 for configuring.docbook).

By default the 6 old unused translations are still in the translation 
catalogs. 
From a technical pov reverting the commit does not break string freeze, 
because old unused translation will be reused on merging, so the translation 
will have the same status as the day before you removed the autobracket 
feature: 
Teams with translation of these strings before will get them back for free, 
all other teams have no translation of these strings.

But because formally the revert breaks string freeze, please ask on kde-i18n-
doc@kde.org immediately and for sure you'll get approval from translators.

Thanks for caring about translation issues.

-- 
Burkhard Lück

_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]