integrate with ShareLaTeX.com

Hey,

I have licensed the translations repo under MIT which should be ok. Other repos such as the web one have semi complicated OS licences, look at the readme for details.

Henryoswald (talk)‎

Thanks. "Semi complicated OS licences" is not particularly helpful I must say... In your example, I see IconShock icons are just fair use? Debian would not be amused but we're not as strict, let's forget it. But I don't see any default license for files other than *.coffee, *.less and silk icons: what's the license for all the tex, json, jpeg, js etc. etc. files I see in there? Forgive me the nitpicks, better safe than sorry. :)

Nemo (talk)‎

Hey,

I understand this is worth getting correct from the start. This project didn't start out being open source, originally it was just a little side project to learn some new techniques but then it grew! I have updated the licence, https://github.com/sharelatex/web-sharelatex/blob/master/README.md let me know if thats good for you.

Henryoswald (talk)‎

Thanks, looks ok. Sorry for the legal screening, now time for Siebrand's ultimate i18n review.

Nemo (talk)‎

Hi,

is there any update on this?

Henryoswald (talk)‎

For reference for this thread, I submitted a patchset gerrit:132683.

SPQRobin (talk)‎

@Henryoswald: the already existing translations are de, fr-FR, and en-US. For consistency it might be best to use language-only locales (i.e. fr, en, ...) when there are no separate versions for countries (yet). This is also what translatewiki.net is used to. Were the FR and US tags deliberately used?

SPQRobin (talk)‎

Henryoswald, we're almost ready to enable ShareLaTeX.com, thanks to Robin. He identified there are only three more things to do: «

The messages in the attribution page (at the end) may not work in all languages since the links are excluded

Language code harmonization: there's de, en-US, fr-FR; it would be best to always use root codes

A lot of Camel Case words, I'd prefer normal capitalization

»

Nemo (talk)‎