[Kst] [kst] [Bug 330050] New: i18n + l10n issues in kst2
Burkhard Lueck
lueck at hube-lueck.de
Thu Jan 16 22:56:27 UTC 2014
https://bugs.kde.org/show_bug.cgi?id=330050
Bug ID: 330050
Summary: i18n + l10n issues in kst2
Classification: Unclassified
Product: kst
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: i18n
Assignee: kst at kde.org
Reporter: lueck at hube-lueck.de
1) Not extracted + untranslated gui strings:
1a) kst-plot(master)$ wcgrep addItem |grep -v "tr("|grep '"'|wc
69 strange strings like "DashDotDotLine"
1b) wcgrep setTypeName graphics/kst-plot/|grep -v "tr("|grep '"'|wc
14 strings used eg in caption of context menu ("Arrow Menu")
2) it is impossible to translate msgs like "P1" or "P2" properly whithout
context (Point 1 / Point 2)
3) A lot of QT_TR_NOOP calls like:
3a) const QString Equation::staticTypeString = QT_TR_NOOP("Equation");
3b) const QString Equation::staticTypeTag = QT_TR_NOOP("equation");
same for image histogram, plugin etc
QT_TR_NOOP is only for msg extraction to the catalog, but does not make a
string translated!
Where are the tr() calls for these const?
Where are the string from 3b) visible in the GUI? Afaik nowhere, so do not
extract them
4) All Dynamic Properties in ui files are marked as translation in designer-qt,
e.g.
label bold, label italic, and many many more (~100)
Are these strings really user visible in the GUI?
I seriously doubt that!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kst
mailing list