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-description = Description
fields-description-placeholder = Text to show inside the field when it's empty
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-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:`
Editor Field Descriptions (#1476) * Add description input to fields dialog QLineEdit seems like the best option, as it saves space and motivates users to keep their descriptions concise. * Add setDescriptions to note initialization script Went for the extra function instead of including it in setFields to prevent potential add-on breakages. * Add tooltip next to field name if description is set * Refactor code according to suggestions Set default tooltip placement to right instead of bottom Use .get() for fld["description"] Fix tab order in fields dialog Swap out abbreviation "desc" for full length name to keep consistency * Update Protobuf and Rust for description Add description to notetypes.proto and schema11 Co-authored-by: RumovZ <RumovZ@users.noreply.github.com> * Fix tooltips not updating with description Remove redundant variable tooltipOptions Update previousTooltip within reactive function * Move LabelDescription out of LabelName Co-authored-by: Henrik Giesel <hgiesel@users.noreply.github.com> * Decrease icon size and fix alignment Co-Authored-By: Henrik Giesel <hengiesel@gmail.com> * the new key needs to be cleared from fields, not the notetype itself Co-authored-by: RumovZ <RumovZ@users.noreply.github.com> Co-authored-by: Henrik Giesel <hengiesel@gmail.com> Co-authored-by: Damien Elmes <gpg@ankiweb.net> 2021-11-06 00:42:48 +01:00			`fields-description = Description`
Make field description a placeholder inside EditingArea (#1912) * Move field description into EditingArea as placeholder * Prevent insertion of breaks into empty fields to allow :empty CSS selector to also work on fields other than the first one. * Remove redundant setContext from EditingArea * Fix import order * Revert "Prevent insertion of breaks into empty fields" This reverts commit 1615fd5cf441b1047dae6a34265acb9c5cae50b2. * Use class:empty instead of :empty CSS pseudo-class * Restrict description to single line, ellipse overflow * Make description in field dialog a bit clearer 2022-06-17 03:02:30 +02:00			`fields-description-placeholder = Text to show inside the field when it's empty`
merge bulk of qt/ - designer files still to do 2020-11-17 08:42:43 +01:00			`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-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 { "}" }.`