mirror of https://github.com/vladmandic/automatic synced 2026-08-27 15:41:00 +02:00

Files

T

Vladimir Mandic 4b2f38ab7f complete refactor javascript to typescript and reorg frontend files and folders

Signed-off-by: Vladimir Mandic <mandic00@live.com>

2026-05-20 18:08:10 +02:00

description, name, applyTo

description	name	applyTo
Use when editing hint text or other UI strings in localization JSON files; follow the ordered rules below for consistent formatting.	Hint Typography Guidelines	ui/locale/*.json

Hint Typography Guidelines

Hint strings render as HTML. Use this small set of inline tags to keep hints scannable:

 for values: defaults, dropdown enums, specific numerics. Examples: 0.30, Karras, v_prediction, UniPC.
... for cross-references to other UI controls by their exact visible label. Examples: Denoising strength, Use init image, Images tab.
 for proper nouns: model families, datasets, technique names. Examples: SDXL, Flux, ControlNet, YOLO.
<code> for literals: paths, filename tokens, command-line snippets to type or use verbatim. Examples: <code>models/yolo</code>, <code>-seg</code>, <code>[PROMPT]</code>.

Cross-references

Use ... whenever a hint refers to another control by its exact visible label. This includes setting names, tab names, and named buttons.
Match the label exactly, including capitalization and spacing; readers look for the same string in the UI.
Do not use  and  separately for cross-references; always combine them.
Generic concept references (the model, the prompt, the scheduler) stay unstyled.

Refer to the unified generation tab as Images (the ModernUI label). Do not write "Control tab"; that label only exists in legacy Standard UI.
"Control" remains valid as a setting value (No: Control only) or as part of a UI element name (Control input pane), just not as a tab name.

  for a line break within a paragraph.
  for a paragraph break.
 - key: description for a keyed bullet list, used for short enumerations of dropdown values, modes, or numeric brackets. Each bullet's key is bolded; descriptions stay plain.
Do not use <ul>, <li>, Markdown asterisks, or unicode bullets.

Do not bold ad-hoc emphasis;  is reserved for values and, combined with , for cross-references.
Do not use  for filenames, paths, or command tokens; those are literals and use <code>.
Do not reword the inside of <code> blocks; they are literal user-facing strings.
Stay ASCII; prefer semicolons or two sentences over em-dashes. The locale file convention is ASCII-only.

ui/locale/locale_en.json is the source of truth. Other ui/locale/locale_*.json files are auto-generated by cli/localize.js; edit only the English file.
Per-locale corrections live in ui/locale/override_{locale}.json.