Portuguese Website UI Translator
Budget: £250 – £750 GBP
I have a set of English interface strings that power every form, tooltip, and error message across my site, and I need them rendered in clear, natural-sounding Portuguese. This isn’t marketing copy or long-form content; it’s concise, user-facing text that must stay friendly, consistent, and within the original character limits so nothing breaks once the JSON resource file is re-imported.
You will receive:
• A single UTF-8 JSON file containing form labels, placeholders, validation errors, and a handful of status messages (≈700 words total).
• Contextual screenshots so you can see where each string lives in the UI.
What I expect back:
• The same JSON file with the value fields translated to Portuguese (pt-BR preferred, but European PT is acceptable if you can indicate any regionalisms).
• No placeholders, variables, or HTML entities altered.
• A quick sanity check report noting strings that exceeded length constraints or required clarification.
I’m happy to answer terminology questions quickly in Slack or your preferred chat—accuracy is more important than speed, though a two-day turnaround would be ideal.
If you’ve translated web apps before, especially those that rely on i18n libraries such as React-i18next or Vue-i18n, let me know; it helps me trust that the curly-brace variables will survive intact.
You will receive:
• A single UTF-8 JSON file containing form labels, placeholders, validation errors, and a handful of status messages (≈700 words total).
• Contextual screenshots so you can see where each string lives in the UI.
What I expect back:
• The same JSON file with the value fields translated to Portuguese (pt-BR preferred, but European PT is acceptable if you can indicate any regionalisms).
• No placeholders, variables, or HTML entities altered.
• A quick sanity check report noting strings that exceeded length constraints or required clarification.
I’m happy to answer terminology questions quickly in Slack or your preferred chat—accuracy is more important than speed, though a two-day turnaround would be ideal.
If you’ve translated web apps before, especially those that rely on i18n libraries such as React-i18next or Vue-i18n, let me know; it helps me trust that the curly-brace variables will survive intact.