<div class="bbWrapper"><blockquote data-attributes="member: 136803" data-quote="alee12" data-source="post: 1138202"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/community/goto/post?id=1138202"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1138202">alee12 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
I should've been more clear. (Because I haven't gone thru the process myself) I just wanted to understand what the current status like to work with translators to get apps/platforms/websites updated.<br />
<br />
For example,<br />
1. How do they understand the scope of the work? Would you provide static/dynamic contents that require translation page by page?<br />
2. How do you update the "translated" content to the app/website/platform? Do they provide snippets of translated contents and they are updated individually within the tech stack?
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote>I`ll try to answer as best I can.<br />
<br />
<b>How do they understand the scope of the work? Would you provide static/dynamic contents that require translation page by page?</b><br />
<br />
Depends on what you need translated, but usually a website has 2 separate parts that need translations.<br />
<br />
- Static texts: Think buttons, menus, footer links, greeting messages from emails etc. Basically stuff that once written doesnt change. To translate this I give them usually a text file and inside it a JSON array (search for the term in google if you dont know what that is) But this has been a hit and miss, depending on the agency. Recently we prepared a sort of editor, that translators can use to translate static text. The editor is basically a list of all the texts in the base language and text fields for each of the language translations so they have minimal ways to screw it up.<br />
The static texts are difficult to get right, since you need context on some of them to get a proper translation.<br />
Sending context along with each text for a button, menu or email sentance is close to immpossible though.<br />
<br />
- Dynamic texts: Think blog posts, articles, testemonials, pages like terms and conditions and so on.<br />
These are bit easier, since you can just send the agency a bunch of links to the pages in the base language, and you get back a very accurate translation for each of the links (each link -> different page).<br />
The formatting here is a big problem and I`ve yet to come up with a solution.<br />
Translators LOOOOOVE MS Word and what you get back from them is usually badly formated, if at all.<br />
Forget about images in blog posts, they are like invisible to them SMH.<br />
<br />
<b>How do you update the "translated" content to the app/website/platform? Do they provide snippets of translated contents and they are updated individually within the tech stack?</b><br />
<br />
Yes, static texts are updated by hand each time there needs to be something translated, and for the dynamic texts we just use an admin panel, the same one that the site editors use.</div>
