Make article translation easier (side-by-side)
complete
Sonja Lorscheidt
When we publish new articles, we have to translate them into different languages which is done by different teams. We are not aware though of new articles published that shall be translated. The whole
language
idea should be made simpler so that we can see if an article exists in different languages like Wordpress is doing it. Once it is translated, it simply has no link to the original
article. Making changes is almost impossible because you won't find the article in other languages.Please improve this for us. :-)
.
.
.
----- 🥳 UPDATE: SEE PROGRESS:
NOW IN BETA! Please reach out to EMIL@HELPJUICE.COM if you'd like beta access!
Emil Hajric
complete
🔥 We have a major new feature: Knowledge Base Localization / Translations.
You can now:
* Instantly deliver more support – without having to translate articles.
* Automatically translate your entire knowledge base, or article in 1 click.
* Translate any article side by side to 50+ languages!
* Deliver customer support in 50+ languages!
🔥 Read more: https://help.helpjuice.com/languages-and-translations/overview:-multiple-languages-&-localization
Helga Martinez
Emil Hajric: Awesome Emil :)
Common Writer
+1, that will be useful.
Martin Drenkelfort
That sounds like a really good improvement! I can't wait for this feature to be released. It will be a great improvement for the entire translation process!
Emil Hajric
in progress
We would like to hear your thoughts on this one.
Please see the links below:
V8/view
Adam Botterbusch
Emil Hajric: This looks really cool! Currently our knowledge is completely siloed in different language formats and even different management platforms/owners. We would be interested in early access for this feature!
Emil Hajric
Adam Botterbusch: You got it :-)
We'll add you to our BETA list
Torge Funke
Emil Hajric: We are also pretty much interested to test that feature! Great improvement - keep it up!
Adam Botterbusch
Emil Hajric: Any idea on when BETA will be open? Thanks!
Emil Hajric
Adam Botterbusch: It's open! Let me add you to the list!
Om Goeckermann
Emil Hajric: its not clear how to add a whole other language. For instance, we have support staff in Bulgaria, but do not want to add Bulgarian to the entire site. For their understanding though, it would be very helpful to have 'internal' training pages available in Bulgarian.
Emil Hajric
Om Goeckermann: Yeah, you'd just add the KB lang. in the settings page, but leave it out from the actual public KB.
Then, whoever visits teh internal kb, can select to only see the Bulgarian articles!
Helga Martinez
Emil Hajric this is awesome! someone below mentions bentley and i completely agree. One thing that it is not clear for me though:
- When choosing the translation - is the landing page of the translated article the same page as the original text OR can you chose the destination? (e.g. master article in ENG, translate to French and publish in the French AND Belgium landing pages. If yes, do we need to have the same category structure or can this be chosen as well?
Secondly: how good does this work with all the formatting? e.g. all the tabs / accordions hyperlinks etc...?
And indeed seconding the question of ETA?
Hope everyone is doing great :)
Cheers
Emil Hajric
Helga Martinez: Hi Helga!
It'll always choose the ORIGINAL article. So if you're translating an article that was initially written in your French KB, even though English US may be your default, it'll use French KB article as that was the original article.
However, it'll usually 'prefer' articles from the Default Language (which is somethign you can change -- the default language).
Once you create a new localization/translation, it'll recreate all the content except Categories and Related Articles. Categories -- you can translate upon creation of a new KB localization (you'd simply click on 'copy over all content').
Emil Hajric
ETA is 15 days. We believe it'll be ready before, but we dont want to ruin expectations
Denis Omerovic
Hi Everybody,
We would like to hear your thoughts on this one.
Please see the links below:
Om Goeckermann
Denis Omerovic: Holy cr*p that looks awesome. I'm so happy to see this I'm not able to be objectively critical right now. We're talking about huuuge amounts of effort and confusion for lots of people. ETA? (also, just the languages per-page <not even side by side> feature would have been plenty for us, but HJ again provides us a Bentley when I was expecting a decent Lexus.
Alexey Denisov
Denis Omerovic: Again, looks nice. But still, what's the overall logic of this translation usage? The KB interface language will be in different language than the Article. If a user is changing the language on first page, then it should change the language for all content.
Emil Hajric
Alexey Denisov: You can always change your KB interface language. We allow you to have a completely different design based off languages actually
Emil Hajric
omdesign
How good is Google Translate?
It might be useful to run this as a 'first pass' and then have actual translators modify it as needed. This would still save considerable time effort and cost.
Erin Casto
We could greatly benefit from this as well! Although our company is global, our headquarters (and by extension, our entire documentation team) is entirely in the US.
If we had a low-impact way to translate our content, it would help support our international client-base without sending our docs to a third party translation service.
Torge Funke
any news on this specific request?
Thx for the feedback
Load More
→