Site & library translation


This is not really a priority, but I think it'd be useful to have both site & library (mostly site) translated to languages other than English. I could do it for Russian.
That will be indexed by local search engines and probably will spread the library broader.


Ubuntu 13.10 x64 gcc4.8


Sergey Sedreev
December 12, 2013, 4:54 AM

People who work with FIX usually have at least basic knowledge of English, but having translations definitely makes it easier to read the docs and try the product. And it shows the maturity of the product. So, yes, that should attract more people to fix8. But this is low priority task. I can ask my wife to translate the site to Russian. Will it be just a copy of pages or site supports i18n at messages level?

David Dight
December 13, 2013, 11:59 PM

I've turned this into an epic. When we get around to it we will have various issues under this for each language.

David Dight
December 14, 2013, 12:02 AM

The current website is not managed by any CMS. All the html/css are done by hand (me) based on twitter bootstrap. There is no i18n support. Maybe we should migrate it to some sort of CMS (e.g. Drupal). Problem with this is that we probably won't be able to use github pages to host our site since gh-pages only supports static pages.

Sergey Sedreev
December 18, 2013, 5:00 AM

I don't really like CMS. Can we stay as simple as possible? Or use angular/node pair?

David Dight
December 18, 2013, 5:13 AM

Yeah I don't like them much either. However, if we move to something like angularjs/node.js we will still have to find a new home as these won't run on gh-pages either.

It would be nice if we could find someone who would host it for us (with proper cloud management - with fault-tolerance and backup etc). gh-pages is nice in this respect.


David Dight


Sergey Sedreev







Fix versions

Affects versions