diff options
| author | David Faure <faure@kde.org> | 2018-12-03 19:12:31 +0000 |
|---|---|---|
| committer | Sergio Martins <smartins@kde.org> | 2018-12-03 19:12:31 +0000 |
| commit | 722b65a2f0eb80522fb6d019650881d75cf9f63f (patch) | |
| tree | 12c236251e8b7b68d2742858fd9817f5d899e9eb | |
| parent | 9d6ae8b4d940776f64f6b1cf558b0f826aa9c816 (diff) | |
tr-non-literal: talk about QT_TR_NOOP and QT_TRANSLATE_NOOP in the README
CCMAIL: faure@kde.org
| -rw-r--r-- | docs/checks/README-tr-non-literal.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/checks/README-tr-non-literal.md b/docs/checks/README-tr-non-literal.md index 4cf97844..2a8835d5 100644 --- a/docs/checks/README-tr-non-literal.md +++ b/docs/checks/README-tr-non-literal.md @@ -3,3 +3,7 @@ Finds calls to `QObject::tr()` with non literal argument. Example: `tr(myStr.toUtf8());` + +This usage of `tr()` might be incorrect because `lupdate` won't be able to pick up the strings for translation. +If the possible values have been marked with `QT_TR_NOOP` or `QT_TRANSLATE_NOOP`, +then this usage of `tr()` is actually fine, i.e. the clazy warning is a false-positive in that case. |