Text, webpage or document translation? Choose a route and check the result

01Choose the input route, then translate both complete sentences

Use Text translation for a copyable notice. For a public page, use Webpage translation and inspect the extracted scope. Choose Document translation when file structure matters. Translation uses an online service; actual processing, costs and formats depend on the current interface and service response, not this exercise.

1. 1
   Preserve the source version. Select English as source and Chinese as target, and enter both sentences together. Optional context can say internal review of a notice; do not add conditions absent from the source.
2. 2
   Wait for the result or error for the current input. Recheck after changing text or target language; an earlier result is not the new answer. If the service fails, retain the source and review again after recovery or with another authorized service.
3. 3
   Make each of the four decisions below, then check names, units and all exceptions. After fixing a word, reread both sentences: a correct quantity can coexist with an incorrect dispatch restriction.

Orders of 12 units or more qualify for free delivery, except refrigerated items.
Do not dispatch before payment is confirmed.

02Make four decisions with the translation

A wrong answer on row 2 points to an exclusive rather than inclusive threshold. A wrong answer on row 3 points to a missing except clause. A wrong answer on row 4 points to the scope of not and before. Continue to delivery review only when the revised translation agrees with the source on every case.

1. 1
   If webpage extraction translated a title but missed the conditions in the body, repair the source capture or use the complete source text. Do not invent clauses that were never read.
2. 2
   Reopen a downloaded document and check the relevant paragraphs, numbering, tables and footnotes. Successful upload does not establish completed translation or accepted layout.
3. 3
   Compile recurring names as terminology, then inspect every occurrence. Terminology review can help find omissions; a matching term cannot validate sentence-level exceptions or negation.

03Decide which structure must travel with the translation

Consider an illustrative product update with a summary paragraph, a price table and a two-page attachment. Use the text route when readers need only the summary; consider the webpage route when they need a linked page for comparison; inspect the document route when the recipient must continue editing an attachment. Do not shorten the input by turning a table into a string that has lost its column relationships.

Each route exposes a different failure. A passage needs enough supplied context; a webpage needs a complete collected body; a document needs room for longer translated wording. Check a complete small sample before processing the whole source. If the online service is unavailable or returns an error, preserve the input and error state rather than treating an earlier translation as the current result.

04Keep a traceable record for each condition

• Quantity: 12 units or more → the reference translation includes 12 → test both 11 and 12.
• Exception: except refrigerated items → the reference excludes refrigerated items → test 12 refrigerated units separately.
• Negation and time: Do not dispatch before payment is confirmed → the reference prohibits dispatch before confirmation → unknown payment status must not become assumed confirmation.
• Absent from the source: shipping price, stock and approver are unknown; add no invented commitments.

This condition ledger checks the sample’s meaning. A real external notice also needs someone familiar with the business to confirm its policy and wording. No paid translation API was tested and no general quality score is claimed here.

05Missing content and broken layout need different repairs

If the collected webpage preview already lacks the price table, retranslating that same collection will not recover it. Return to the source and check whether the content requires login, expansion or script execution. Where you are allowed to use it, handle the relevant passage separately with explicit table headings and a stated source scope. A truncation notice also needs an explicit record of the unprocessed portion.

If the downloaded document contains all the wording but an English label pushes a table onto another page, fix the layout after checking meaning. Adjust column width or type size in the delivery copy instead of deleting an exception to make the text fit. Record the source version and the labels revised during review so a later update does not reuse an obsolete translation.

06Optional tools for a different input or next step

• Translate a short passage: Use explicit context where needed, then inspect names, quantities and conditional sentences before copying the result.
• Translate a public webpage: Check that the collected body includes the intended content; compare tables, links and image alt text with the source before exporting HTML.
• Translate a document: Confirm the currently supported format and service availability, then compare the downloaded file’s sections and layout with the original.
• Check fixed terminology: Apply a reviewed glossary and inspect collisions or missed terms rather than treating a glossary match as sentence-level correctness.

07When is this notice ready to deliver?

DeepL documents the document-translation request flow; check current service requirements before submitting an attachment.

Use the number, negation and condition review on important translations. Build and check a glossary before a larger translation batch.