Live data from Hacker News

Launch HN: Lang (YC S19) – Internationalization Built for Devs

news.ycombinator.com

31–40 of 48 posts

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#31
post #29

Does using the tooling depend on being translated through Lang? We are going to be setting up new internationalization tooling soon but have a robust human translation community already that we wouldn't want to bypass.

Our tools send the strings to a dashboard. At this point, you can have your own translators add translations and pull them back in. We have developed flows which make it easy for your own translators to go through your phrases, see the context (description + screenshots) and add appropriate translations.

Sending translations to the agencies we've partnered with is completely optional.

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#32
Hi, we developed a similar solution minus the handling of translations itself - fortunately we have inhouse people that can supply that.

A few questions:

- Some translations are a bit context dependant, what happens if I dont agree with the translation? - Sometimes we do some kind of media localization, eg: users in france will see a different image than users in portugal. Are you a translation only shop, or you plan to do some kind of l10n?

Best of luck!

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#33
post #32

Hi, we developed a similar solution minus the handling of translations itself - fortunately we have inhouse people that can supply that. A few questions: - Some translations are a bit context dependant, what happens if I dont agree with the translation? - Sometimes we do some kind of media localization, eg: users in france will see a different image than users in portugal. Are you a translation only shop, or you plan…

Good question, we let you provide as much context to the translators as you want (description, tone, and screenshots). If you still don't like the translation, you can comment and it will be redone taking your comment into account. Additionally, if you have employees who want to review the translations, they can do that on the platform.

We currently handle plan to handle localization of text (regular, dates, currency, time, gender, plurals, etc.). Handling images is interesting though, I would love to explore that more if it was a pain point for you. Ping me at abhi@langapi.co--I'd love to talk!

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#36
We needed recently translate our chrome extension (languagelearningwithnetflix.com) into 18 languages. We are poor and had less than $1000 for the job.

Here's our approach.

1. Move all strings into a Google doc. Takes about 8 hours.

2. Organise strings into groups with screenshots, think carefully, split strings, look for reused strings, reword things to make them simpler and easier to translate, add notes to some strings to make the meaning more explicit. Very tedious part of job, 2-3 days work.

3. Put the doc, editable with link, onto upwork with a fixed payment, somewhat generous for translation wordcount. Check translator is a native in the target language, had some good feedback and ideally some IT/programming experience. Order translations for the languages we can check ourselves (5-6 languages).

4. Check the translations received for issues. Translators typically misinterpret the same things, as the source was not clear enough. Fix these issues. Maybe 4 hours work.

5. Now send to 10+ other translators for the languages we don't understand. Cross fingers that these will be ok.

6. Check translations of labels for homogenous usage of semicolons, capitals, fullstops etc. Struggle with zh/ja/ko.

7. Use a small JS script to transform CSV output from sheets to JSON for chrome.i18n.

8. Cycle through all locales and for overflowing text or other issues.

9. For any extra strings that we might need later, can try Microsoft UI translations database, or else, Google translate (which is mostly ok, can check the reverse translation).

Honestly this all was quite a lot of boring work, but we probably ended up with reasonable translations at a good price, and managed to pay translators reasonable money.

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#37

That's a great product! But... I can't change the language of your website?!

Our site is internationalized with our product and we have Spanish translations. If you change your Chrome language setting to Spanish you can see it. We'll plan to add a manual language flag soon.

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#38
post #35

Looks great! It'd be cool if the homepage was a live demo that allowed you to toggle the language.

Our framework automatically checks the browser language preferences. Change your browser language preference to Spanish and refresh to see the translations. We'll also add the flag toggler soon to make it more obvious.

Re: Launch HN: Lang (YC S19) – Internationalization Built for Devs

#39

We needed recently translate our chrome extension (languagelearningwithnetflix.com) into 18 languages. We are poor and had less than $1000 for the job. Here's our approach. 1. Move all strings into a Google doc. Takes about 8 hours. 2. Organise strings into groups with screenshots, think carefully, split strings, look for reused strings, reword things to make them simpler and easier to translate, add notes to some st…

> Struggle with zh/ja/ko.

FYI, these are frequently called CJK (chinese, japanese, korean). Although, that more has to do with the fact that each character takes multiple keystrokes to type and thus is harder to support, than to do with the locale.

Post reply on HN