Topic on Talk:Content translation

If would be so much easier if we could also edit source code directly, sure I can publish a page and do it then but sometimes there are so many things it's just easier to start it on my own. You could hide it under some advanced tab if you think most users don't want it. Still something deleting one word or changing one little thing in code would get it to look so much better. Otherwise I like this tool a lot! Great work!

Hi,

Can you give an example of things that are easier for you to do in source code?

Sure, here are couple

1. often Templates are wrong and with little bit of editing it can be fixed, then most that are even right are just copied as they are in English and you can't translate those fields unless you have access to source code of that article.
2. If something is quoted again it is just copied "as is" in English and you can't translate until you publish the page and edit the source
3. Similar thing happens with math formulas and pronunciation text as well but it can be easily fixed once you publish the page
4. Text under images is sometimes impossible to edit or really hard (can't navigate through it so you have to delete entire translation if you need to change one word)
5. Editing Phylogeny tree is not possible

Those are just couple I could think of right now, there are probably more.

Most of these issues are with templates. It is possible to edit most templates in Visual Editor, and the current version of Content Translation uses the same tools for template editing as Visual Editor does. Have you tried it? The Phylogeny template is perhaps too complicated, but most others are usable through Visual Editor.

Sure it is possible to enter templates in some cases but often it is not possible. I have tried to edit it in VIsual editor but even when it is possible to edit templates often it's not possible to edit all fields, some fields you can only edit in code. Still I do think it would be a lot easier if it was possible to edit it in code. Sure editing in code is not for everyone but it should at least be an option for those who want to use it. Then I don't expect everything to be directly transferable and being able to edit it in code sure would help a lot with it.

P.S. I wasn't just thinking about Phylogeny template, but also regular Phylogeny tree even though both of those I assume are complicated they would be easily editable in code.

Then I understand why feature won't be added, you are thinking if you want to edit in code just edit it normally like most people and just use Google translate. Still I do think this tool has a lot to offer and makes so many things easier when translating.

Thanks for hearing me out!

No, not necessarily. It's actually possible that source editing will be added some day. Other people have requested it, too. It's not planned for the immediate future, but it may happen further down the road. I'm just trying to suggest solutions for now.

Oh okey. Hope it does become availble sooner rather then later.

Thanks for your help!