anki/ftl/core/search.ftl

## Errors shown when invalid search input is encountered.
## Backticks change the text formatting, so please don't change the backticks.
## Text inside backticks should not be changed unless noted.
## It's ok to change quotes outside of backticks however, eg:
## "`{ $context }`" => 「`{ $context }`」

search-invalid-search = Invalid search: { $reason }
search-misplaced-and = an `and` was found but it is not connecting two search terms. If you want to search for the word itself, wrap it in double quotes: `"and"`.
search-misplaced-or = an `or` was found but it is not connecting two search terms. If you want to search for the word itself, wrap it in double quotes: `"or"`.
# Here, the ellipsis "..." may be localised.
search-empty-group = a group `(...)` was found, but there was nothing between the brackets to search for. If you want to search for literal brackets, wrap them in double quotes: `"( )"`.
search-unopened-group = a closing bracket `)` was found, but there was no opening bracket `(` preceding it. If you want to search for a literal `)`, wrap it in double quotes or prepend a backslash: `")"` or `\)`.
search-unclosed-group = an opening bracket `(` was found, but there was no closing bracket `)` following it. If you want to search for a literal `(`, wrap it in double quotes or prepend a backslash: `"("` or `\(` .
search-empty-quote = a pair of double quotes `""` was found, but there was nothing between them to search for. If you want to search for literal double quotes, prepend backslashes: `\"\"`.
search-unclosed-quote = an opening double quote `"` was found, but there was no second one to close it. If you want to search for a literal `"`, prepend a backslash: `\"`.
search-missing-key = a colon `:` was found, but there was no keyword preceding it. If you want to search for a literal `:`, prepend a backslash: `\:`.
search-unknown-escape = the escape sequence `{ $val }` is not defined. If you want to search for a literal backslash `\`, prepend another one: `\\`.
search-invalid-argument = `{ $term }` was given an invalid argument '`{ $argument }`'.
search-invalid-flag-2 = `flag:` must be followed by a valid flag number: `1` (red), `2` (orange), `3` (green), `4` (blue), `5` (pink), `6` (turquoise), `7` (purple) or `0` (no flag).
search-invalid-prop-operator = `prop:{ $val }` must be followed by one of the following comparison operators: `=`, `!=`, `<`, `>`, `<=` or `>=`.
search-invalid-other = please check for typing mistakes.

## eg. expected a number in "due>5x", but found "5x"

search-invalid-number = expected a number in "`{ $context }`", but found "`{ $provided }`".
search-invalid-whole-number = expected a whole number in "`{ $context }`", but found "`{ $provided }`".
search-invalid-positive-whole-number = expected a positive whole number in "`{ $context }`", but found "`{ $provided }`".
search-invalid-negative-whole-number = expected a whole number less than or equal to 0 in "`{ $context }`", but found "`{ $provided }`".
search-invalid-answer-button = expected an answer button between 1-4 in "`{ $context }`", but found "`{ $provided }`".

## Column labels in browse screen

search-note-modified = Note Modified
search-card-modified = Card Modified

##

# Tooltip for search lines outside browser
search-view-in-browser = View in browser
Make AnkiError::SearchError work with ParseError Use mock ftl strings for now. 2021-01-14 11:14:55 +01:00			`## Errors shown when invalid search input is encountered.`
add another example and tweak wording at top 2021-01-22 02:00:19 +01:00			`## Backticks change the text formatting, so please don't change the backticks.`
			`## Text inside backticks should not be changed unless noted.`
			`## It's ok to change quotes outside of backticks however, eg:`
more parsing error tweaks The majority of the error checking can now be delegated to routines like parse_f32(), parse_negative_i32() and so on, instead of creating specific error messages for each type. 2021-01-19 06:48:23 +01:00			## "`{ $context }`" => 「`{ $context }`」
Make AnkiError::SearchError work with ParseError Use mock ftl strings for now. 2021-01-14 11:14:55 +01:00
search error tweaks - use markdown instead of HTML, to make editing and translating easier - use a shared prefix - a few very minor wording tweaks - we don't need to translate undocumented command errors - share a string for positive number of days - share a string for invalid property and state arguments, and avoid listing them out Related discussion: https://github.com/ankitects/anki/pull/922 2021-01-16 06:37:40 +01:00			`search-invalid-search = Invalid search: { $reason }`
			search-misplaced-and = an `and` was found but it is not connecting two search terms. If you want to search for the word itself, wrap it in double quotes: `"and"`.
			search-misplaced-or = an `or` was found but it is not connecting two search terms. If you want to search for the word itself, wrap it in double quotes: `"or"`.
Fix HTML formatting for search errors 2021-01-15 09:43:36 +01:00			`# Here, the ellipsis "..." may be localised.`
search error tweaks - use markdown instead of HTML, to make editing and translating easier - use a shared prefix - a few very minor wording tweaks - we don't need to translate undocumented command errors - share a string for positive number of days - share a string for invalid property and state arguments, and avoid listing them out Related discussion: https://github.com/ankitects/anki/pull/922 2021-01-16 06:37:40 +01:00			search-empty-group = a group `(...)` was found, but there was nothing between the brackets to search for. If you want to search for literal brackets, wrap them in double quotes: `"( )"`.
minor ftl tidy-up before commit 2021-01-20 00:12:27 +01:00			search-unopened-group = a closing bracket `)` was found, but there was no opening bracket `(` preceding it. If you want to search for a literal `)`, wrap it in double quotes or prepend a backslash: `")"` or `\)`.
			search-unclosed-group = an opening bracket `(` was found, but there was no closing bracket `)` following it. If you want to search for a literal `(`, wrap it in double quotes or prepend a backslash: `"("` or `\(` .
			search-empty-quote = a pair of double quotes `""` was found, but there was nothing between them to search for. If you want to search for literal double quotes, prepend backslashes: `\"\"`.
			search-unclosed-quote = an opening double quote `"` was found, but there was no second one to close it. If you want to search for a literal `"`, prepend a backslash: `\"`.
			search-missing-key = a colon `:` was found, but there was no keyword preceding it. If you want to search for a literal `:`, prepend a backslash: `\:`.
			search-unknown-escape = the escape sequence `{ $val }` is not defined. If you want to search for a literal backslash `\`, prepend another one: `\\`.
search error tweaks - use markdown instead of HTML, to make editing and translating easier - use a shared prefix - a few very minor wording tweaks - we don't need to translate undocumented command errors - share a string for positive number of days - share a string for invalid property and state arguments, and avoid listing them out Related discussion: https://github.com/ankitects/anki/pull/922 2021-01-16 06:37:40 +01:00			search-invalid-argument = `{ $term }` was given an invalid argument '`{ $argument }`'.
search-invalid-flag -> search-invalid-flag-2 2021-06-02 08:53:23 +02:00			search-invalid-flag-2 = `flag:` must be followed by a valid flag number: `1` (red), `2` (orange), `3` (green), `4` (blue), `5` (pink), `6` (turquoise), `7` (purple) or `0` (no flag).
more parsing error tweaks The majority of the error checking can now be delegated to routines like parse_f32(), parse_negative_i32() and so on, instead of creating specific error messages for each type. 2021-01-19 06:48:23 +01:00			search-invalid-prop-operator = `prop:{ $val }` must be followed by one of the following comparison operators: `=`, `!=`, `<`, `>`, `<=` or `>=`.
search error tweaks - use markdown instead of HTML, to make editing and translating easier - use a shared prefix - a few very minor wording tweaks - we don't need to translate undocumented command errors - share a string for positive number of days - share a string for invalid property and state arguments, and avoid listing them out Related discussion: https://github.com/ankitects/anki/pull/922 2021-01-16 06:37:40 +01:00			`search-invalid-other = please check for typing mistakes.`
add another example and tweak wording at top 2021-01-22 02:00:19 +01:00
			`## eg. expected a number in "due>5x", but found "5x"`

more parsing error tweaks The majority of the error checking can now be delegated to routines like parse_f32(), parse_negative_i32() and so on, instead of creating specific error messages for each type. 2021-01-19 06:48:23 +01:00			search-invalid-number = expected a number in "`{ $context }`", but found "`{ $provided }`".
			search-invalid-whole-number = expected a whole number in "`{ $context }`", but found "`{ $provided }`".
			search-invalid-positive-whole-number = expected a positive whole number in "`{ $context }`", but found "`{ $provided }`".
			search-invalid-negative-whole-number = expected a whole number less than or equal to 0 in "`{ $context }`", but found "`{ $provided }`".
minor ftl tidy-up before commit 2021-01-20 00:12:27 +01:00			search-invalid-answer-button = expected an answer button between 1-4 in "`{ $context }`", but found "`{ $provided }`".
update edited/changed column labels https://github.com/ankitects/anki/pull/674/files 2020-06-29 10:34:03 +02:00
			`## Column labels in browse screen`

			`search-note-modified = Note Modified`
			`search-card-modified = Card Modified`

			`##`
automatically format/check ftl files 2020-11-22 06:30:59 +01:00
Add button in dynDeckConf to search in browser 2021-02-01 13:55:03 +01:00			`# Tooltip for search lines outside browser`
			`search-view-in-browser = View in browser`