2. Futon
3. Arabic (Algerian)

-- Android strings-- Use this for components with app/src//res//values*/strings.xml

Please translate UI strings keeping placeholders, markup and plural forms intact.

• Keep placeholders exactly as in source: {0}, %1$s, {name}, <xliff:g id="X">…</xliff:g>, etc.

• Preserve HTML/XML tags and entity escapes (&, \n).

• Use correct ICU plurals and gender forms when present.

• Keep tone concise and user-facing; avoid adding or removing meaning.

• If context is missing, check code comments or ask reviewers. Mark unresolved items with a comment.

  Example: Source "Found %1$d results" → Translate as "Encontrados %1$d resultados".

  -- Android strings (expanded) -- Purpose: UI strings used in the app. Translators should follow these rules:

• Context: These strings appear in the UI. Keep translations short and natural for mobile screens.

• Placeholders: Do not reorder, rename or remove placeholders. If source uses %1$s or {name}, keep the same token and positional indices.

• Plurals: Follow ICU plural rules. Ensure all plural categories required by the target language are present.

• Markup & escaping: Keep XML/HTML tags and escape sequences unchanged. For complex inline formatting, prefer preserving tags rather than moving text outside them.

• Tone & style: Use friendly, concise tone consistent with the app. Prefer imperative for actions (e.g., "Delete" vs "Deletes"), use formal/informal according to project guidelines (specify below if applicable).

• Screenshots/context: Use comments or attached screenshots for ambiguous strings. Use the Weblate comments for doubts.

• Quality checks: Verify placeholders, tag balancing, and correct plural forms before marking as reviewed.

  Note: short description has an 80 character limit — adapt concisely.