joomla/Component-Builder
joomla/Component-Builder
39
23
Fork 11
Code Issues 82 Pull Requests Projects 4 Wiki Activity

Updated 035 Translation Mananger in JCB explained (markdown)

Amigo 2019-07-24 11:10:12 +02:00
parent f8835e4994
commit 467c546da1
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
035-Translation-Mananger-in-JCB-explained.md

@ -75,10 +75,10 @@ In the document manager, in component in JCB, you will see there is a new tab ca
[00:13:21](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m21s)
There are two ways to get to the strings. The one is like I show you via the component. We are planning to add a button here. Whereby you can import these and export these strings quite easily so that you could give them to other team members who can make translations, give back to you and you just import them here, and then it gets linked automatically. That is still under development.
There are two ways to get to the strings. The one is like I showed you via the component. We are planning to add a button whereby you can import these and export these strings quite easily so that you could give them to other team members who can make translations, and give it back to you and then you can import it, and then it gets linked automatically. That is still under development.
* ### Go To Language Translations
[00:14:03](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m03s)
The other way to get to these translations is simply to go to language translations. Here you'll find all the components strings together. This could become a database with over 8000 lines. But like you see it's working quite well. I've already got a lot of components mapped. The ones that you see usually are the ones that are active which I'm working on. I've got quite a few in archive as well. [00:14:36](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m36s) I've been testing this again, say 8 or 9 components at the same time, sharing strings among each other, and I expect this feature to become quite powerful. As soon as we are able to speed up the translation method. There is been suggestions that we also add this feature to a community area somewhere. Where we you can push your English strings there, and you can pull already translated strings from it. [00:15:15](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m15s) I know this is a great idea but how to manage that, so that we don't find people abusing the system are still under the debate. Anyone have any good suggestions please go to GitHub and open a issue and let's start talking. Well I hope this is enough explanation on how to do multiple language implementation on your components in Joomla Component Builder. I'm quite happy about this new feature. I really think it will in the long run become a very valuable asset.
The other way to get to these translations is to go to Language Translations, where all the component strings are together. This could become a database with over 8000 lines but it works quite well. I already have a lot of components mapped. The ones that are displayed are usually the ones that are active. I got quite a few in archive as well. [00:14:36](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m36s) I have tested this against 8 or 9 components at the same time, sharing strings among each other. I expect this to become a very powerful tool as soon as we are able to speed up the translation method. There has been suggestions that we add this feature to a community area where you can push English strings, and can pull already translated strings from it. [00:15:15](https://www.youtube.com/watch?v=zzAcVkn_cWU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m15s) This is a great idea but how to manage it so that the system does not get abused, are still under the debate. Go to GitHub and open a issue if you have any suggestions.