Language that works inside your digital product
Localize website content, software strings and applications with attention to interface context, technical variables and the target market.
Website content and customer journeys
Website localization covers the paths a user follows, from a landing page to a product description, form or support article. Explain who the audience is and what the page should help them do.
Share brand terminology, product names and approved messaging. Search titles and descriptions should be written for the target language and the page’s actual purpose rather than copied word for word.
Resource files and variables
Software strings can contain placeholders, markup, plural forms and other technical elements. Provide the relevant file formats and identify elements that must remain unchanged.
A string without context can be ambiguous. Screenshots, feature descriptions and developer notes help distinguish a command, status message, field label or error explanation.
UI strings and display context
Buttons, menus and notifications need clear, concise language that fits the available space. State any character limits and explain whether strings are combined dynamically in the interface.
Agree whether the scope includes reviewing the translation in the product. Linguistic review of a file and testing a functioning interface are different tasks with different access requirements.
Games and market-facing content
Game text also depends on character voice, relationships, narrative timing and the player’s choices. A style guide, character notes and a terminology list help maintain a coherent experience.
Store descriptions, release notes and help content should use the same product vocabulary as the interface. Clarify which channels and assets are included in each release.
What to include in your enquiry
Send the complete source or a representative sample, the source and target languages, and the intended use. Identify the current file versions and any passages that are outside the translation scope.
Add your deadline, preferred delivery format and approved reference material. If the work involves layout, confirmation, testing or another additional task, state it explicitly so the quotation covers the required output.
Questions before you begin
Do you need access to our product?
Screenshots and context notes may be enough for some projects. If in-product review is requested, agree the test environment, access permissions and review scope before providing access.
How is the price calculated?
The quote depends on the language pair, source volume, specialist subject, file quality, formatting and requested delivery. Send the actual material so these factors can be assessed.
Can I request a specific deadline?
Yes. State when you need the translation and share the complete source. Availability and delivery timing are confirmed after reviewing the scope; an enquiry alone does not confirm a booking.
How should I share confidential documents?
Discuss confidentiality, access and any required agreement with the team before sending the complete sensitive material. A non-sensitive sample can help begin the scope discussion.
Discuss your requirements with Tri Viet
Send your source files or describe the work, language pair and deadline. We will review the scope before confirming the quotation and delivery arrangements.
