2. ONLYOFFICE Web Apps
3. Turkish

Translation Guidelines for ONLYOFFICE Web Apps

String format

• Strings use positional placeholders like {0}, {1}, {2}. Do NOT translate or remove them — they are replaced with values at runtime.
• Some strings contain HTML tags (<br>, <b>, </b>, <a>, etc.). Preserve all HTML tags exactly as they appear in the source.

Key naming conventions

• Keys prefixed with DE. belong to Document Editor
• Keys prefixed with PE. belong to Presentation Editor
• Keys prefixed with SE. belong to Spreadsheet Editor
• Keys prefixed with PDFE. belong to PDF Editor
• Keys prefixed with VE. belong to Visio Editor
• Keys prefixed with Common. are shared across editors.
• Some shared keys have editor-specific variants with a suffix (e.g., warnUpdateExternalDataDE vs warnUpdateExternalDataPE) — translate each according to its editor context.
• This may help you choose the right context for ambiguous terms.

General rules

• Keep translations concise — UI space is limited, especially in toolbar buttons and menus.
• Use formal tone (e.g., "vous" in French, "Sie" in German, "Вы" in Russian) unless your language community prefers informal.
• Do not translate product names: ONLYOFFICE, Document Editor, Spreadsheet Editor, Presentation Editor, PDF Editor, Visio Editor.
• Keyboard shortcuts (e.g., Ctrl+C, Shift+Enter) should follow platform conventions for your locale but keep the key names recognizable.

Questions?

If you are unsure about context, check the live editors to see where a string appears in the UI.