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

Multi-language pages should be a first-class citizen #317

Open
kreativitea opened this issue Jul 23, 2018 · 3 comments
Open

Multi-language pages should be a first-class citizen #317

kreativitea opened this issue Jul 23, 2018 · 3 comments

Comments

@kreativitea
Copy link

kreativitea commented Jul 23, 2018

Feature Request:

With notifications in play now, true multi-language pages should be a priority. Members who are set up as owners of individual pages should also get notifications when the second language of a page is edited, in order to ensure the original page is compliant with the updated information.

@sotarok
Copy link
Member

sotarok commented Jul 24, 2018

Thank you for the feedback.
Yes, we know that it is really important to decide how to handle and manage multi-language (mixed-language) contents.
Currently, we have plans below:

  • Make pages have locale settings on itself.
  • Link pages between different language pages.
  • Make it possible to view a kind of easily understandable another language page since the page updated. (I'm still looking for the best way for realize it)

@kreativitea
Copy link
Author

kreativitea commented Jul 26, 2018

@sotarok thanks! Where do I find the roadmap for this project? Also, I don't mind implementing it myself, or helping to find resources to work on it.

https://github.com/crowi/crowi/wiki/Roadmaps

^ 1.6 is supposed to have i18n, but on the actual 1.6 page it only has the backward compat breakage for elasticsearch.

@sotarok
Copy link
Member

sotarok commented Jul 26, 2018

@kreativitea Thank you for your support!
Sorry the roadmap pages are not up to date. (We're going to update those pages soon.)

Yes, 1.6 has i18n feature. It means the core UI supports English and Japanese. But as I said, the design for multi-language contents is a bit difficult because Wiki's contents are not made by us but by its users.
(Features included 1.6.x listed here)

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

No branches or pull requests

2 participants