[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: qDebug messages i18n'ed?
From: Nick Shaforostoff <shafff () ukr ! net>
Date: 2016-04-15 9:39:45
Message-ID: 1460712781.515086997.tsszed37 () frv38 ! fwdcdn ! com
[Download RAW message or body]
> in kfilemetadata (git repo of the same name) there are messages like
> these:
> qDebug() << i18n("Plugin could not be converted to a WriterPlugin");
> qDebug() << i18n("Plugin could not create instance") << pluginPath;
>
> Is it common to use qDebug() to bring messages to the user? I mean, can
> qDebug() not be disabled and then the user does not see the messages?
> Although these messages read rather technical, so maybe they are not
> meant for mere users and should be de-i18n'ed?
>
> In case of intended translatability, the 2nd message might need a %1
> thingy so translators know there is something coming and can rearange
> and all.
debug should not be i18n-ed, it's real use is posting the output to bug reports which \
should be in english. user visible strings should be presented via gui
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic