2. AniSync
3. AniSync
4. Portuguese (Brazil)

Welcome to AniSync translations!

Thank you for helping make AniSync accessible to more people around the world.

Important guidelines

Placeholders

Some strings contain placeholders like %s, %d, %1$s, or %2$s. These are replaced dynamically by the app (e.g., a username or episode number).

Always keep these placeholders exactly as they appear — same symbol, same order. Example:

• English: Episode %1$d airs in %2$s

• Correct: Episodio %1$d se estrena en %2$s

• Incorrect: Episodio %2$s se estrena en %1$d

  Special characters

• & is an escaped ampersand (&). Keep it as & unless your language uses a different conjunction symbol.

• \' is an escaped apostrophe. You can usually replace it with a regular apostrophe in your language if appropriate.

  Accessibility strings (a11y)

  Strings starting with a11y_, cd_, or content_description are used by screen readers for visually impaired users. Translate them as concise, descriptive phrases. Example:

• cd_like → "Like" (not "Thumbs up icon")

  Notification channels

  Strings under notification_channel_* appear in Android system settings. Keep them short (under 40 characters if possible) since they appear in list headers.

  App name

  The app name AniSync should remain unchanged across all languages unless your language requires a different script (e.g., Arabic or Japanese could use a phonetic transliteration if culturally appropriate).

Style and tone

• Consistent terminology: If you translate "Library" as "Biblioteca", use "Biblioteca" everywhere. Check existing translations in your language for consistency.

• Keep it concise: UI labels, button text, and snackbar messages should be brief. Long text may be truncated on smaller screens.

Review process

• Suggested translations are reviewed before merging.
• You can comment on any string to ask for context or discuss the best phrasing.
• Machine translation suggestions are provided as a starting point — please review and correct them before submitting.

Need help?

• Open a GitHub Discussion for questions about context or terminology.