-
Notifications
You must be signed in to change notification settings - Fork 23
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
Documenting translation approaches #166
Comments
Sure! Just write in multiple languages. I do this all the time |
If you want to do translated versions of a page (like in Wikipedia), just add subhypha with language code, like |
If the names of the articles are sufficiently different in different languages, you can name them differently, like Apple and Pomme. |
Thank you, will give it a look 💯 |
Apologies for so much noise but I'd like to re-open this one with a request: if I have |
How does the engine know that a specific subhypha is a translation? |
I'm not sure of the internals... maybe (mis-)using hypha is not the correct approach? Feel free to close. I would document the current translation work-around in #166 (comment) though to save work telling the next person? I would say that figuring out some sort of engine support for this would be ideal and flag "first class" translation support in mycorrhiza. |
I don't see why document it in the engine, different approaches fit different wikis. Some would translate titles, some would have sub-hyphae, some would have separate wikis. An overview of different organization of translations would make a good article on https://mycorrhiza.wiki though! I don't like the idea of first class translations. |
How do you do multilingual pages? Is it already supported?
The text was updated successfully, but these errors were encountered: