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

Documenting translation approaches #166

Closed
decentral1se opened this issue Aug 23, 2022 · 8 comments
Closed

Documenting translation approaches #166

decentral1se opened this issue Aug 23, 2022 · 8 comments

Comments

@decentral1se
Copy link
Contributor

How do you do multilingual pages? Is it already supported?

@bouncepaw
Copy link
Owner

Sure! Just write in multiple languages. I do this all the time

@chekoopa
Copy link

chekoopa commented Aug 23, 2022

If you want to do translated versions of a page (like in Wikipedia), just add subhypha with language code, like Some Section/A Particular Page/ru. It seems like a poor workaround, but seemingly better than having a whole dedicated language wiki, like Wikia Fandom does.

@bouncepaw
Copy link
Owner

If the names of the articles are sufficiently different in different languages, you can name them differently, like Apple and Pomme.

@decentral1se
Copy link
Contributor Author

Thank you, will give it a look 💯

@decentral1se
Copy link
Contributor Author

decentral1se commented Aug 24, 2022

Apologies for so much noise but I'd like to re-open this one with a request: if I have foo & foo/french then indeed I get this lovely sub-hypha button at the bottom. However, and here is the problem, the button is at the bottom, not the top! Most people who don't speak, say, english, as default, will probably leave the page without knowing that at the very bottom of the page, there is a button to the french translation (imagine the page is long...). Of course, I can add this myself at the top of the page with a link but it would also be nice to perhaps signal somehow that a sub-hpyha is a language translation page so that is appears at the top?

@decentral1se decentral1se reopened this Aug 24, 2022
@decentral1se decentral1se changed the title Multilingual pages? Mark sub-hypha as language translation hypha for ease of discovery? Aug 24, 2022
@bouncepaw
Copy link
Owner

How does the engine know that a specific subhypha is a translation?

@decentral1se
Copy link
Contributor Author

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.

@bouncepaw
Copy link
Owner

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.

@decentral1se decentral1se changed the title Mark sub-hypha as language translation hypha for ease of discovery? Documenting translation approaches Aug 27, 2022
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

3 participants