Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multilingual tours not exported as such #33

Open
hannolans opened this issue Oct 24, 2012 · 1 comment
Open

Multilingual tours not exported as such #33

hannolans opened this issue Oct 24, 2012 · 1 comment

Comments

@hannolans
Copy link
Contributor

Now TAP has functionality for multilingual tours, I am trying to export a tour as a multilingual tour.

  1. I create a tour node, translate this node in another language
  2. I create stops, and create translations for that stops in the named tour
    So far, that works fine.

But when doing an export as bundle or doing an export as xml, I don't get get correct stops. That means:

  • Stops are not labeled with their correct language (lang="nl")
  • Translated stops are not appearing, only the original stops

Two questions:

  • is translating individual stops the right way to create a tour in another language?
  • If so, is the code correct in requesting the correct translation of a node, and is the language for a tour correctly transfered to function that builds a stop?
@hannolans
Copy link
Contributor Author

After investigating I see that the CMS only renders a node in one language, and not for all languages at once as in the specification of tourML.
I have succesfully patched the code that it renders all the titles at once, but have problems with including the sources for each language in an asset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant