mis-matched translation of 'projects' page (EN - RU)

[cccs-ip]

Marcus notes:

When migrating the translated materials, I noticed that the Russian translation of the Projects-page does not match the English content on Mezzanine. I just wanted to let you know that I didn't transfer it, as I want to hear with you first -- the code is extremely messy.

[cccs-ip]

This seems to be OK with

http://crossculturalconsult.com/index.php/en/projects

http://crossculturalconsult.com/index.php/ru/projects

...

http://crossculturalconsult.com/index.php/en/projects/projects-theme

http://crossculturalconsult.com/index.php/ru/projects/projects-theme

...

http://crossculturalconsult.com/index.php/en/projects/projects-theme/international-social-development

http://crossculturalconsult.com/index.php/ru/projects/projects-theme/international-social-development

... where should I be looking?

[cccs-ip]

FYI - it appears that the easiest way to access translation content for pages is via the Joomla front end, which you get at by logging in here:

http://crossculturalconsult.com/login

once you log in, you should see a little 'edit' icon appear in the top left corner of each of the content sections. it looks like a pencil on paper. when you press it (for each language) it lets you access the content using an editor. you can toggle to HTML and that will give you the 'publication version' of each page.

most content appears to be correct as a one-to-one translation. I added in a lot of the 'project' translations for Russian using this approach.

please let me know if you have any troubles.

[marcusbjoerkqvist]

Yes, it appears the source of confusion lies in that the Joomla HTML is nothing at all like what appears on the front-end. I'll use the translations from the front-end instead.

[cccs-ip]

Thanks. Yeah, I think some pages in the back-end (Russian version) were old but not deleted. Translation content was hidden under 'FaLang' in the backend, but even there one couldn't access it all. Please re-check the pages you entered initially and confirm that you have the latest HTML used in the front end.

Thanks!