Commit e3752612 authored by Jérome Perrin's avatar Jérome Perrin

web_renderjs_ui: use consistent term for "Invalid Search Criteria"

We sometimes used "Invalid search criteria", sometimes "Invalid Search
Criteria". Unify to use "Invalid Search Criteria" everywhere
parent 208a3b43
......@@ -3543,9 +3543,6 @@ msgstr "无效的日期或时间"
msgid "Invalid Search Criteria"
msgstr "无效搜索条件"
msgid "Invalid search criteria"
msgstr "无效的搜索条件"
msgid "Invalidate"
msgstr "废止"
......
......@@ -5,7 +5,7 @@
data-i18n=No such document was found
data-i18n=Create New
data-i18n=Explore the Search Result List
data-i18n=Invalid search criteria
data-i18n=Invalid Search Criteria
data-i18n=You are offline
data-i18n=Unexpected server error
-->
......
......@@ -414,7 +414,7 @@
error.hash.expected.length === 1 &&
error.hash.expected[0] === "'QUOTE'") {
return gadget.getTranslationList([
"Invalid search criteria"
"Invalid Search Criteria"
])
.push(function (translation_list) {
return gadget.notifyInvalid(translation_list[0]);
......
......@@ -73,7 +73,7 @@
Actually, this popup is displayed on internal query "syntax" error.
This error will be fixed later and so the popup won't be shown anymore. -->
<td>waitForTextPresent</td>
<td>Invalid search criteria</td>
<td>Invalid Search Criteria</td>
<td></td>
</tr>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment