anki/ftl/core/fields.ftl

fields-add-field = Add Field
fields-delete-field-from = Delete field from { $val }?
fields-editing-font = Editing Font
fields-field = Field:
fields-field-name = Field name:
fields-fields-for = Fields for { $val }
fields-font = Font:
fields-new-position-1 = New position (1...{ $val }):
fields-notes-require-at-least-one-field = Notes require at least one field.
fields-remember-last-input-when-adding = Remember last input when adding
fields-reverse-text-direction-rtl = Reverse text direction (RTL)
fields-size = Size:
fields-sort-by-this-field-in-the = Sort by this field in the browser
fields-that-field-name-is-already-used = That field name is already used.
fields-name-first-letter-not-valid = The field name should not start with #, ^ or /.
fields-name-invalid-letter = The field name should not contain :, ", { "{" } or { "}" }.
merge bulk of qt/ - designer files still to do 2020-11-17 08:42:43 +01:00			`fields-add-field = Add Field`
			`fields-delete-field-from = Delete field from { $val }?`
			`fields-editing-font = Editing Font`
			`fields-field = Field:`
			`fields-field-name = Field name:`
			`fields-fields-for = Fields for { $val }`
			`fields-font = Font:`
			`fields-new-position-1 = New position (1...{ $val }):`
			`fields-notes-require-at-least-one-field = Notes require at least one field.`
			`fields-remember-last-input-when-adding = Remember last input when adding`
			`fields-reverse-text-direction-rtl = Reverse text direction (RTL)`
			`fields-size = Size:`
			`fields-sort-by-this-field-in-the = Sort by this field in the browser`
			`fields-that-field-name-is-already-used = That field name is already used.`
Reject field name with : { or } More than {{ is acceptable to start a tag, which means that `{{{Foo}}` won't be interpreted as "the content of `Foo`" and should be rejected. For the sake of clarity and parsing, I suspect that those symbol should be rejected elsewhere too. Similary `{{Foo}}}` won't be interpreted as "Show the content of field `Foo}`" even if this field exists, so it's better to reject `}`. It's clearly necessary to reject "}}" inside the field name, rejecting "}" seems easier to explain and avoid future unexpected problem if the templates change. The ":" are used to separate filters, and rejecting it in field name would ensure that there is no ambiguity. 2020-12-27 10:07:56 +01:00			`fields-name-first-letter-not-valid = The field name should not start with #, ^ or /.`
fix ftl formatting 2021-01-04 04:27:35 +01:00			`fields-name-invalid-letter = The field name should not contain :, ", { "{" } or { "}" }.`