Translation and Accessibility

Translation and Accessibility

FolderView Plus ships versioned language catalogs with English fallback, production locales, regional aliases, and pseudo-locales for layout testing.

Translation model

• English is the source catalog and fallback.
• Modern messages are organized into namespaces.
• A generated legacy-surface namespace covers remaining static/dynamic UI text.
• Runtime diagnostics reports namespace coverage and potentially stale translations.
• Locale aliases map Unraid/browser locale forms to canonical catalogs.

Do not edit only one generated locale file. Source changes require catalog regeneration and structural guards.

Message rules

• Preserve $1, $2, and other parameters exactly.
• Preserve HTML/attribute intent and do not add unsafe markup.
• Keep product names and technical identifiers consistent.
• Translate destructive actions precisely; do not soften delete/replace/restore warnings.
• Use the glossary/context and screenshots when a short label is ambiguous.
• Review plural forms and regional language differences.

Right-to-left and pseudo-locales

Arabic is a production RTL catalog. en-XA stresses expansion/accented text, while ar-XB stresses RTL and mixed technical content. Passing pseudo-localization does not replace real Arabic review, especially for names, paths, ports, and versions.

Contributor workflow

1. Update English source and catalog version as required.
2. Regenerate catalogs using the repository scripts.
3. Translate with UI context.
4. Run localization and language-usage guards.
5. Test production locale plus pseudo-locales in browser fixtures.
6. Review destructive/security/privacy wording manually.
7. Update locale status only after complete accepted coverage.

See the authoritative translation guide and platform setup.

Accessibility expectations

• All primary tasks must be keyboard reachable.
• Managed dialogs trap focus, support Escape/backdrop policy where safe, restore focus, and announce status.
• Focus indicators must remain visible in supported themes.
• Status cannot rely on color alone.
• Reduced-motion preferences must be respected.
• Text must remain usable at browser zoom and smartphone widths.
• Mixed RTL/LTR technical content must remain readable.

Report a translation or accessibility problem

Use the repository issue chooser. Include locale, browser, Unraid/plugin versions, exact page/control, expected wording/behavior, and privacy-reviewed screenshot. Translation contributions should target dev.