search

bouncepaw / mycorrhiza

🍄📑 Filesystem and git-based wiki engine for the independent web written in Go and using Mycomarkup as its primary markup language.
https://mycorrhiza.wiki
GNU Affero General Public License v3.0
300 stars 26 forks source link

Documenting translation approaches #166

Closed decentral1se closed 1 year ago

decentral1se commented 2 years ago

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

bouncepaw commented 2 years ago

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

chekoopa commented 2 years ago

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 commented 2 years ago

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

decentral1se commented 2 years ago

Thank you, will give it a look :100:

decentral1se commented 2 years ago

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?

bouncepaw commented 2 years ago

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

decentral1se commented 2 years ago

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 https://github.com/bouncepaw/mycorrhiza/issues/166#issuecomment-1224052449 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 commented 2 years ago

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.