Checks and fixups¶
The quality checks help catch common translator errors, ensuring the translation is in good shape. The checks can be ignored in case of false positives.
Once submitting a translation with a failing check, this is immediately shown to the user:
Automatic fixups¶
In addition to Quality checks, Weblate can also fix some common errors in translated strings automatically. Use it with caution to not have it add errors.
参考
Quality checks¶
Weblate employs a wide range of quality checks on strings. The following section describes them all in further detail. There are also language specific checks. Please file a bug if anything is reported in error.
Translation checks¶
Executed upon every translation change, helping translators maintain good quality translations.
BB コード マークアップ¶
BBcode in translation does not match source
BBCode represents simple markup, like for example highlighting important parts of a message in bold font, or italics.
This check ensures they are also found in translation.
注釈
The method for detecting BBcode is currently quite simple so this check might produce false positives.
連続した重複重複単語¶
Text contains the same word twice in a row:
バージョン 4.1 で追加.
Checks that no consecutive duplicate words occur in a translation. This usually indicates a mistake in the translation.
ヒント
This check includes language specific rules to avoid false positives. In case it triggers falsely in your case, let us know. See Reporting issues in Weblate.
スペースが連続¶
Translation contains double space
Checks that double space is present in translation to avoid false positives on other space-related checks.
Check is false when double space is found in source meaning double space is intentional.
Formatted strings¶
Checks that formatting in strings are replicated between both source and translation. Omitting format strings in translation usually causes severe problems, so the formatting in strings should usually match the source.
Weblate supports checking format strings in several languages. The check is not enabled automatically, only if a string is flagged appropriately (e.g. c-format for C format). Gettext adds this automatically, but you will probably have to add it manually for other file formats or if your PO files are not generated by xgettext.
This can be done per unit (see Additional info on source strings) or in Component configuration. Having it defined per component is simpler, but can lead to false positives in case the string is not interpreted as a formatting string, but format string syntax happens to be used.
ヒント
In case specific format check is not available in Weblate, you can use generic プレースホルダー.
Besides checking, this will also highlight the formatting strings to easily insert them into translated strings:
AngularJS 補間文字列¶
AngularJS interpolation strings do not match source
Named format string |
|
Flag to enable |
angularjs-format |
C 言語書式¶
C format string does not match source
Simple format string |
|
Position format string |
|
Flag to enable |
c-format |
C# 言語書式¶
C# format string does not match source
Position format string |
|
Flag to enable |
c-sharp-format |
ECMAScript テンプレート リテラル¶
ECMAScript template literals do not match source
Interpolation |
|
Flag to enable |
es-format |
i18next 補間¶
The i18next interpolation does not match source
バージョン 4.0 で追加.
Interpolation |
|
Nesting |
|
Flag to enable |
i18next-interpolation |
Java 形式¶
Java format string does not match source
Simple format string |
|
Position format string |
|
Flag to enable |
java-format |
Java MessageFormat¶
Java MessageFormat string does not match source
Position format string |
|
Flag to enable |
java-messageformat enables the check unconditionally |
auto-java-messageformat enables check only if there is a format string in the source |
JavaScript 形式¶
JavaScript format string does not match source
Simple format string |
|
Flag to enable |
javascript-format |
% のプレースホルダー(補完)¶
The percent placeholders do not match source
バージョン 4.0 で追加.
Simple format string |
|
Flag to enable |
percent-placeholders |
Perl 書式¶
Perl format string does not match source
Simple format string |
|
Position format string |
|
Flag to enable |
perl-format |
PHP 書式¶
PHP format string does not match source
Simple format string |
|
Position format string |
|
Flag to enable |
php-format |
Python のブレース書式¶
Python brace format string does not match source
Simple format string |
|
Named format string |
|
Flag to enable |
python-brace-format |
Python 書式¶
Python format string does not match source
Simple format string |
|
Named format string |
|
Flag to enable |
python-format |
Qt フォーマット¶
Qt format string does not match source
Position format string |
|
Flag to enable |
qt-format |
Qt 複数形式¶
Qt plural format string does not match source
Plural format string |
|
Flag to enable |
qt-plural-format |
Ruby 書式¶
Ruby format string does not match source
Simple format string |
|
Position format string |
|
Named format string |
|
Named template string |
|
Flag to enable |
ruby-format |
翻訳済み¶
This string has been translated in the past
Means a string has been translated already. This can happen when the translations have been reverted in VCS or lost otherwise.
不一致¶
This string has more than one translation in this project or is not translated in some components.
Weblate checks translations of the same string across all translation within a project to help you keep consistent translations.
The check fails on differing translations of one string within a project. This can also lead to inconsistencies in displayed checks. You can find other translations of this string on the Other occurrences tab.
注釈
This check also fires in case the string is translated in one component and not in another. It can be used as a quick way to manually handle strings which are not translated in some components just by clicking on the Use this translation button displayed on each line in the Other occurences tab.
You can use 自動翻訳 addon to automate translating of newly added strings which are already translated in another component.
Kashida 文字の使用¶
The decorative kashida letters should not be used
バージョン 3.5 で追加.
The decorative Kashida letters should not be used in translation. These are also known as Tatweel.
マークダウンの参照¶
Markdown link references do not match source
バージョン 3.5 で追加.
Markdown link references do not match source.
翻訳の最大長¶
Translation should not exceed given length
Checks that translations are of acceptable length to fit available space. This only checks for the length of translation characters.
Unlike the other checks, the flag should be set as a key:value
pair like
max-length:100
.
ヒント
This checks looks at number of chars, what might not be the best metric when using proportional fonts to render the text. The 翻訳の最大長 check does check actual rendering of the text.
The replacements:
flag might be also useful to expand placeables before
checking the string.
翻訳の最大長¶
Translation rendered text should not exceed given size
バージョン 3.7 で追加.
Translation rendered text should not exceed given size. It renders the text with line wrapping and checks if it fits into given boundaries.
This check needs one or two parameters - maximal width and maximal number of lines. In case the number of lines is not provided, one line text is considered.
You can also configure used font by font-*
directives (see
Customizing behavior), for example following translation flags say that the
text rendered with ubuntu font size 22 should fit into two lines and 500
pixels:
max-size:500:2, font-family:ubuntu, font-size:22
ヒント
You might want to set font-*
directives in Component configuration to have the same
font configured for all strings within a component. You can override those
values per string in case you need to customize it per string.
The replacements:
flag might be also useful to expand placeables before
checking the string.
n が合っていないもの¶
Number of n in translation does not match source
Usually escaped newlines are important for formatting program output.
Check fails if the number of \\n
literals in translation do not match the source.
コロンが一致していません¶
Source and translation do not both end with a colon
Checks that colons are replicated between both source and translation. The presence of colons is also checked for various languages where they do not belong (Chinese or Japanese).
省略記号が一致していません¶
Source and translation do not both end with an ellipsis
Checks that trailing ellipses are replicated between both source and translation.
This only checks for real ellipsis (…
) not for three dots (...
).
An ellipsis is usually rendered nicer than three dots in print, and sounds better with text-to-speech.
感嘆符が一致していません¶
Source and translation do not both end with an exclamation mark
Checks that exclamations are replicated between both source and translation. The presence of exclamation marks is also checked for various languages where they do not belong (Chinese, Japanese, Korean, Armenian, Limbu, Myanmar or Nko).
終止符が一致していません¶
Source and translation do not both end with a full stop
Checks that full stops are replicated between both source and translation. The presence of full stops is checked for various languages where they do not belong (Chinese, Japanese, Devanagari or Urdu).
疑問符が一致していません¶
Source and translation do not both end with a question mark
Checks that question marks are replicated between both source and translation. The presence of question marks is also checked for various languages where they do not belong (Armenian, Arabic, Chinese, Korean, Japanese, Ethiopic, Vai or Coptic).
セミコロンが一致していません¶
Source and translation do not both end with a semicolon
Checks that semicolons at the end of sentences are replicated between both source and translation. This can be useful to keep formatting of entries such as desktop files.
改行数の不一致¶
Number of new lines in translation does not match source
Usually newlines are important for formatting program output.
Check fails if the number of \n
literals in translation do not match the source.
複数形の欠如¶
Some plural forms are not translated
Checks that all plural forms of a source string have been translated. Specifics on how each plural form is used can be found in the string definition.
Failing to fill in plural forms will in some cases lead to displaying nothing when the plural form is in use.
プレースホルダー¶
Translation is missing some placeholders:
バージョン 3.9 で追加.
Translation is missing some placeholders. These are either extracted from the
translation file or defined manually using placeholders
flag, more can be
separated with colon, strings with space can be quoted:
placeholders:$URL$:$TARGET$:"some long text"
句読点の間隔¶
Missing non breakable space before double punctuation sign
バージョン 3.9 で追加.
Checks that there is non breakable space before double punctuation sign (exclamation mark, question mark, semicolon and colon). This rule is used only in a few selected languages like French or Breton, where space before double punctuation sign is a typographic rule.
正規表現¶
Translation does not match regular expression:
バージョン 3.9 で追加.
Translation does not match regular expression. The expression is either extracted from the
translation file or defined manually using regex
flag:
regex:^foo|bar$
同じ複数形¶
Some plural forms are translated in the same way
Check that fails if some plural forms are duplicated in the translation. In most languages they have to be different.
文頭の改行¶
Source and translation do not both start with a newline
Newlines usually appear in source strings for good reason, omissions or additions can lead to formatting problems when the translated text is put to use.
参考
先頭の空白¶
Source and translation do not both start with same number of spaces
A space in the beginning of a string is usually used for indentation in the interface and thus important to keep.
文末の改行¶
Source and translation do not both end with a newline
Newlines usually appear in source strings for good reason, omissions or additions can lead to formatting problems when the translated text is put to use.
参考
文末の空白¶
Source and translation do not both end with a space
Checks that trailing spaces are replicated between both source and translation.
Trailing space is usually utilized to space out neighbouring elements, so removing it might break layout.
未変更の翻訳¶
Source and translation are identical
Happens if the source and corresponding translation strings is identical, down to at least one of the plural forms. Some strings commonly found across all languages are ignored, and various markup is stripped. This reduces the number of false positives.
This check can help find strings mistakenly untranslated.
The default behavior of this check is to exclude words from the built-in
blacklist from the checking. These are words which are frequently not being
translated. This is useful to avoid false positives on short strings, which
consist only of single word which is same in several languages. This blacklist
can be disabled by adding strict-same
flag to string or component.
安全でない HTML¶
The translation uses unsafe HTML markup
バージョン 3.9 で追加.
The translation uses unsafe HTML markup. This check has to be enabled using
safe-html
flag (see Customizing behavior). There is also accompanied
autofixer which can automatically sanitize the markup.
参考
The HTML check is performed by the Bleach library developed by Mozilla.
URL¶
The translation does not contain an URL
バージョン 3.5 で追加.
The translation does not contain an URL. This is triggered only in case the unit is marked as containing URL. In that case the translation has to be a valid URL.
XML マークアップ¶
XML tags in translation do not match source
This usually means the resulting output will look different. In most cases this is not a desired result from changing the translation, but occasionally it is.
Checks that XML tags are replicated between both source and translation.
ゼロ幅スペース¶
Translation contains extra zero-width space character
Zero-width space (<U+200B>) characters are used to break messages within words (word wrapping).
As they are usually inserted by mistake, this check is triggered once they are present in translation. Some programs might have problems when this character is used.
Source checks¶
Source checks can help developers improve the quality of source strings.
省略¶
The string uses three dots (...) instead of an ellipsis character (…)
This fails when the string uses three dots (...
) when it should use an ellipsis character (…
).
Using the Unicode character is in most cases the better approach and looks better rendered, and may sound better with text-to-speech.
長期間未翻訳¶
The string has not been translated for a long time
バージョン 4.1 で追加.
When the string has not been translated for a long time, it is can indicate problem in a source string making it hard to translate.
複数の整合性に問題¶
The translations in several languages have failing checks
Numerous translations of this string have failing quality checks. This is usually an indication that something could be done to improve the source string.
This check failing can quite often be caused by a missing full stop at the end of a sentence, or similar minor issues which translators tend to fix in translation, while it would be better to fix it in the source string.
複数の無名変数¶
There are multiple unnamed variables in the string, making it impossible for translators to reorder them
バージョン 4.1 で追加.
There are multiple unnamed variables in the string, making it impossible for translators to reorder them.
Consider using named variables instead to allow translators to reorder them.
複数形でない¶
The string is used as plural, but not using plural forms
The string is used as a plural, but does not use plural forms. In case your translation system supports this, you should use the plural aware variant of it.
For example with Gettext in Python it could be:
from gettext import ngettext
print ngettext('Selected %d file', 'Selected %d files', files) % files