Replies: 3 comments 2 replies
-
Hi @DavidPeix, Thank you for taking the time to submit this suggestion! I need to understand how you work with this, to better get a grip about what you need. Our developers work directly with the .xlf files, without going through the extra step by adding a comment.
Above works very well when only working with languages that you can fully translate yourself. But if you, as a developer, only want to do partial translation this can be messy for the ones that will do the rest of the translations ( In those scenarios we use the setting Have you tried any of above workflows? |
Beta Was this translation helpful? Give feedback.
-
Hi Johannes
Thank you for your answer.
I’d be super happy to perform a quick demo if you want ? I’m available next Friday afternoon between 3 and 6 pm 😊
Have a nice day
David
Le 13 juin 2022 à 13:36, Johannes Wikman ***@***.***> a écrit :
Hi @DavidPeix<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidPeix&data=05%7C01%7Cdpeixoto%40absyscyborg.com%7Cddebc5577da14c88844708da4d30eb99%7Ccacec9c1efee4ae8bf5c5458075e5b69%7C0%7C0%7C637907169757436376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Y6SVVRE7gQE2I9VSA7X27M2dPRstLHhIL8Bw797hTf0%3D&reserved=0>,
Thank you for taking the time to submit this suggestion!
I need to understand how you work with this, to better get a grip about what you need.
Adding the translations as code seems a bit strange (or at least "old fashioned") to me, so I guess you need to persuade me into doing this... ;-)
Our developers work directly with the .xlf files, without going through the extra step by adding a comment.
1. Write code, with English texts on all captions, labels etc.
2. Build solution to update the g.xlf file
3. Execute the NAB: Refresh XLF files from g.xlf command, which compares the translation units in the g.xlf file with all the other language-xlf files and inserts, updates, removes translation units as needed.
4. Go through all not translated texts (all marked with [NAB: ]) with Ctrl+Alt+U and do the translations
5. Commit + push
Above works very well when only working with languages that you can fully translate yourself.
But if you, as a developer, only want to do partial translation this can be messy for the ones that will do the rest of the translations ([NAB: ] tags all over the place...)
In those scenarios we use the setting NAB.UseExternalTranslationTool, so that the NAB: Refresh XLF files from g.xlf command changes the state attribute, instead of inserting [NAB: ] tags. In that way you can select what you, as a developer, wants to translate or not - and leave the rest to someone else.
Have you tried any of above workflows?
If so, what issues do you have with that? Is it something we could fix there instead?
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjwikman%2Fnab-al-tools%2Fdiscussions%2F387%23discussioncomment-2937708&data=05%7C01%7Cdpeixoto%40absyscyborg.com%7Cddebc5577da14c88844708da4d30eb99%7Ccacec9c1efee4ae8bf5c5458075e5b69%7C0%7C0%7C637907169757436376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wg6q0fOtuMj5GF4Ek8jAZp%2FhtR6BgGNmIoRGuEjrtKs%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALJYL7MUGLN2TTFCWMVXVE3VO4MKZANCNFSM5YTWGAXQ&data=05%7C01%7Cdpeixoto%40absyscyborg.com%7Cddebc5577da14c88844708da4d30eb99%7Ccacec9c1efee4ae8bf5c5458075e5b69%7C0%7C0%7C637907169757436376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=y6Nni%2B2GRBTT3IazINy%2BV4HtslJluT552xSqOoLW48U%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello, For example, a table field might be defined as such:
Which, after compiling and synchronizing the XLF files, creates something like this:
And using a command would result in this:
|
Beta Was this translation helpful? Give feedback.
-
Hi Johannes,
My name is David, I'd like to suggest a small improvement of NAB AL tool to you :
The idea being to allow a developer to create language. xlf files taking the benefit of his/her natural languages (English and French for example in France) thanks to a procedure going through some kind of already indentified snippets located in al code.
We already did half of the job to generate the xlf file from the code, and would love to help providing what we did, and give you the opportunity to take the lead on the futur improvements ?
Looking forward to get your opinion on that, I wish you a pleasant day.
David
Beta Was this translation helpful? Give feedback.
All reactions