Faʻaliliuina mai Peretania i le Saina

PT ZH Faʻaiuga vave API avanoa

Faʻaliliuina... O le a faʻaalia iinei le faʻaliliuina...

Toe faʻaigoaina o faila

Fausia se teugatupe saoloto e faʻaliliuina ai faʻamaumauga, subtitles, ma isi.

Saini mo le saoloto Fesoʻotaʻiga

Faʻafefea ona Faʻaliliuina le Portuguese i le Chinese

1
Tuʻu lau tekinolosi

Taʻu poʻo le peʻe lau tekinolosi Portuguese i totonu o le pusa faʻatumu i luga. E mafai ona e faʻatumu e oo atu i le 10,000 faʻailoga, poʻo le faʻapipiʻiina o se faʻamaumauga.

2
kiliki Faʻaliliuina

Kiliki le ki o le Faʻaliliuina poʻo le faʻatali - o le faʻaliliuina otometi o le a amataina pe a e taofi le tipiina. O le AI e faʻavasega lau tusitusiga i ni nai sekone.

3
Faʻaigoa lau Faʻaliliuina

O lau faʻaliliuina o le Chinese o le a faʻaalia i le taimi lava e tasi. Kiliki le ki o le kope e kope ai i lau pusatusi, poʻo le fesoʻotaʻi atu e ala i la matou API.

Faʻamaufaʻailoga masani Portuguese

Kiliki i soo se faaupuga e faʻaliliuina ai i le taimi lava e tasi.

Faʻaliliuina vave

Toe maua faʻaliliuina mai le Portuguese i le Chinese i milisekone.

Tuʻuina atu o faʻamatalaga

Faʻapipiʻi le Word, PDF, SRT subtitles ma isi mo le faʻaliliuina o le batch.

Fesoasoani API

Integrate lenei faʻaliliuina o le paʻi i totonu o au talosaga ma la matou REST API.

Portuguese i le Chinese API

Faʻaopopo lenei paʻi faʻaliliuina i lau talosaga ma se valaau API faigofie.

Vaʻai i faʻamatalaga API Faʻatumu le API Key 
curl -X POST https://api.translateapi.ai/api/v1/translate/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "Hello", "source_language": "pt", "target_language": "zh"}'

E uiga i le Portuguese i le Chinese Faʻaliliuina

O le TranslateAPI e tuʻuina atu ai le vave ma le saʻo o le Portuguese i le Chinese faʻaliliuina e ala i le AI alualu i luma.

  • Faʻaliliuina o le Tusi - Faʻaliliuina soʻo se tusitusiga e oo atu i le 10,000 faʻailoga i le taimi lava e tasi
  • Faʻaliliuina o faʻamatalaga - Faʻapipiʻi faila Word, PDF, ma faʻamatalaga mo le faʻaliliuina
  • API Integration - Faʻaopopo le faʻaliliuina mai o le Portuguese i le Chinese i au talosaga
  • Faʻaliliuina - Faʻaliliuina o fuaiupu e tele i se talosaga tasi
Faʻaaoga mataupu:
  • Faʻaliliuina faila mai le Portuguese i le Chinese mo pisinisi
  • Faʻafanua 'upega tafaʻilagi ma talosaga mai le Portuguese i le Chinese
  • Convert Portuguese subtitles to Chinese
  • Fesoʻotaʻi ma tagata talaʻi Chinese
Faʻaliliuina
Faʻavae
Peretania (pt)
Atinaʻe
Saina (zh)

Faʻamatalaga Faʻatonu

CJK ↔ Latin translation faces three distinct challenges: word-segmentation in the CJK source (no spaces), kanji / hanzi ambiguity (one character → multiple readings), and English noun-phrase compounding. The model is trained on bilingual corpora that handle all three; expect roughly 90-93% professional-grade accuracy for Portuguese ↔ Chinese.

For Chinese-side output the default is simplified hanzi (the standard in Mainland China and Singapore). Pass the explicit code zh-TW or zh-HK if you need traditional characters for Taiwan / Hong Kong audiences.

Japanese output uses the conventional kanji + hiragana + katakana mix: kanji for content words and inflectional stems, hiragana for grammatical particles and verb endings, katakana for foreign loanwords and emphasis. The model picks the right script context-by-context.

Yes — output Hangul is always composed (NFC-normalized syllable blocks, not decomposed jamo). Mixed Hangul + Hanja (Sino-Korean characters) is supported when the target convention calls for it (legal, academic, classical text).

For Chinese: the simplified-vs-traditional pair is fixed by the language code, and pinyin readings are not exposed in the output by default. For Japanese: the model uses on'yomi vs kun'yomi based on context; name furigana (above-the-line reading hints) is preserved if it was in the source.

Yes — CJK punctuation marks (。 ， 、 ： ； ！ ？ "..." 「」 『』 （）) are emitted in the script-appropriate full-width form. Latin output gets standard half-width punctuation. The width is set per output, not carried from input.

Person names follow the convention of the target audience: Eastern names (Last First) stay in that order for CJK output and flip to First-Last for English. Place names use the most-common English spelling (Beijing not Peking, Tokyo not Tōkyō). Company names use the spelling on the company's own English-language site.

When translating INTO Japanese or Korean, the model defaults to the polite formal register (です/ます for Japanese, 합니다 for Korean) which is the safe choice for business and technical content. Casual or sonkeigo/keigo (elevated honorific) registers need explicit hints in the source.

Chinese and Japanese have no inter-word spaces; Korean has them. When translating from a Latin-script source the model adds spaces correctly for Korean output and omits them for Chinese/Japanese output. The reverse direction handles segmentation automatically.

Code blocks (anything inside triple-backticks or <code> tags) pass through unchanged. Inline code spans (single-backtick) also stay literal. Identifier-style terms (camelCase, snake_case, file paths) are preserved; comment prose around them is translated.

Technical accuracy for Portuguese ↔ Chinese is highest in software, e-commerce, and consumer-electronics domains where bilingual corpora are abundant. Specialist legal and medical content benefits from glossary-augmented translation (POST the glossary as a sidecar to the API).

CJK languages encode roughly 1.7-2x more meaning per character than English, so a 5,000-character English source typically produces 2,800-3,400 characters of CJK output. The 10,000-character per-request limit on the web translator is character-counted on the source side.

Isi filifiliga o le faʻaliliuina

E sili atu mai le Portuguese

Faʻaliliuina le Portuguese i isi gagana

Vaʻai i mea uma
Faʻatulagaga

Faʻaliliuina mai le Chinese i le Portuguese

Saina → Peretania
Vaʻai i uma gagana e lagolagoina
Faʻavasega lenei itulau
Faafetai mo lau iloiloga!
/5 Faavae i luga o Faʻailoga