Open bnomis opened 8 years ago
Multilingual support is something that would be great but would require a substantial effort from one or more contributors to do the translation for the large number of pages we already have, plus perhaps more important the ongoing maintenance.
I know the ruby language site supports multiple languages - I haven't looked at how their workflow supports this but would that would be a good place to understand more.
For the moment, I'm going to consider this out of scope, but would be happy to hear more in the comments. Another alternative is of course to fork the site, translate it, and host it yourself under a different url (while satisfying the other license constraints).
We are not interested in using a CMS, thanks.
In terms of forking and hosting by your self on github.io, there were some obstacles we faced when working with the original repo. (Have not fully investigated the cause, but it does not work out of the box) Could you please consider making the configuration compatible with github.io hosting?
Hello,
Which language are you interested in supporting? Japanese?
We do not host on github.io and instead have a CI, hosting, and caching infrastructure that requires the site to be set up the way it is, so I am unable to make changes in that regard (unless they are changes that would not affect the way we publish the site). I do not have time to research what those changes would be but if you suggested something, I'd be willing to try it to see if it is compatible.
Also, I want to note that while the content contained in this repository is EPL, the other design elements of the site (logo, images, styling, etc) are not EPL and may not be published without the consent of Rich Hickey.
I am interested in providing either the support for or hosting of translations in other languages, but unfortunately it's difficult for me to make that a high priority for the team right now.
Alex
Hi Alex!
Thanks for the response!
Yes the target language was Japanese.
Basically how to host the content was the main concern for starting the translation and we were exploring options, which one of them was to make use of the official clojure-site.
However, with your clarification on the design elements (Was not aware, so thanks), I think it is easiest for the time being to set up something on our own based on the content that is EPL and host it somewhere.
Will keep an eye on the official hosting of other languages coming!
@puredanger
So time has passed and there is a Japanese translation project slowly but steadily progressing: https://github.com/japan-clojurians/clojure-site-ja
Basically we are rolling our own themes and publishing on github.io. Challenges are that the directory structures of the original project make it difficult to tell jbake to generate urls that are suitable for hosting on github.io.
Is there a chance for the translations to be hosted in a similar setup? This would be ideal as we can focus on maintaining the adoc translations.
Otherwise we are considering to turn the translation site into a SPA to simplify the publishing process.
Thanks for taking a look!
@puredanger Is this still in backlog status?
Basically saying it would be ideal if our translated adocs can be hosted in a similar setup as the original site, but if that is still low priority we will look for/build a non jbake solution to host the translations on github.io for the time being.
I think we'd open to hosting the translated site in a similar way to clojure.org, but that would likely require a fair amount of time on my part just to do the resource setup (includes storage, DNS, SSL, caching, site search, and CI). The only person likely to do this work is me and I will not be available to look at it until after EuroClojure (about a month from now). I would appreciate another ping here then to remind me.
@puredanger Really appreciate the positive reply!
I will definitely give a ping after EuroClojure.
P.S. Looking forward to the dependency heaven talk video! :) (Wish I could go...)
@puredanger
Here is the ping a month later, but no rush :)
@puredanger ?
@puredanger ?
@puredanger Just want to explore some options to reduce the work maintaining the Japanese translation project here. Setting up a different Jbake theme for the Japanese project requires a lot of effort so it would be really great if either you can host the Japanese translations or give some permission to re-use the official Jbake theme. Thanks!
I suggest the new clojure.org be made in more than one language.
If there's interest, I can contribute a mulit-lingual CMS http://yajogo.com/en/
Thanks
Simon