France has put work into this so makes sense to follow their lead. This will help other people maintaining the user guide to act with ease. Similarly it would be great if we can create an automated push notification of a diff when a file is changed. This will make it easier for a user guide maintainer to easily make updates using any translation system that they choose. The actual gains in productivity will come from having a similar structure of the user guides between countries. Then we gain financially if the automation saves us enough time that it pays for itself.įrom some back-of-envelope calcs I don’t really think that we are at that point yet. The big cost is the initial integration such that a new page provided results in an auto-API call. The plans are thus very flexible and scale-able. Team plans that reduce the price when you have 3 users or more. Individual plans 5.99 euro for 5 translations /month or 19.99 euro for 20 translations Personally for UK I would pay for a tool that provided an automatic translation for any user guide pages that France creates if it was saving us money. In summary I agree with your conclusion that it doesn’t make sense to automate now. Sounds like this will be a great tool though it will require development etc. Pinging also (put I can’t find her) for English, because it goes also the other way around. It would be fair to pay for it, but I think I would prefer seeing people updating guides be paid first.īut I would love to have other feedback on especially if you already though of a Spanish version after the Catalan if you have some time to play with the Portuguese translator it could be interesting as for German and Dutch However we can use this tool manually to be more quick into updating our guides in several languages. To conclude, my personal opinion is that I don’t see us working on a automated tool for this now. Today however, DeepL only translate to a limited set of languages yet: It wouldn’t be perfect but it would let the word out. With an automated tool, we could have our guides translated in languages we don’t have within the community yet. Today you need to speak English to understand what OFN does. ![]() With absolutely no reviews, this idea would be great in order to onboard more countries into using OFN. So I guess this is what you had in mind when you were thinking about this tool? To maybe connect it to Gitbook and automate translation? If you pay a plan you can access the API. ![]() For example, order cycles are translated “cycle de commande” in French but we are currently using “Cycle de vente” (Sales cycles). More generally it will also need reviews because we need it to fit the correct terms we have on the platform. In both French and German, it didn’t know how to translate the pronoun “you”, alternating between “vous/Sie” the polite way and “Du/tu” the familiar way. For example, in French sometimes the word “hub” was translated as “Moyeu”. However, this is not a tool we can let translate things on its own. They claim the documents and data are deleted when you are finished.You can upload entire documents (but only Microsoft licensed at the moment).The quality of the translation is not bad at all. You can also use my testing account (credentials in bidwarden) especially if you don’t want to be limited by batch of 5000 characters. ![]() You can find the translator available here freely:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |