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

Language support? #21

Open
OsnaFonz opened this issue Oct 28, 2015 · 8 comments
Open

Language support? #21

OsnaFonz opened this issue Oct 28, 2015 · 8 comments

Comments

@OsnaFonz
Copy link
Collaborator

Is it possible to make this little Gem language independent?

@Arachnid
Copy link
Collaborator

Yes! All the text is either in the template, or in the list of parts. If those are translated, it would be straightforward to choose between them - assuming the simpler option isn't just to copy and translate the whole thing.

What it needs is someone fluent in languages other than English to do the translation work.

@OsnaFonz OsnaFonz reopened this Oct 29, 2015
@OsnaFonz
Copy link
Collaborator Author

OsnaFonz commented Nov 4, 2015

Ok, i think that we wait until we think that the english version is nearly OK. Then i duplicate the index.html to index_de.html for example for a german version and begin to translate it.
alternatively we can put the template into an extra file. i tested this but then you can't open the file on an local computer.

@Arachnid
Copy link
Collaborator

Arachnid commented Nov 4, 2015

Rather than putting the template in a separate file, we can use a separate 'script' tag, and choose which to use based on the language setting.

@bithalver
Copy link
Contributor

Erm, maybe I do not understand all things, but if we duplicate the index.html then later we have to correct all mistakes in all copied index.hmtl files, right ?
Can we use instead some resource file with all the text ? That way the translation could be very easy (and does not need any understanding of code).
My two cents.

@Arachnid
Copy link
Collaborator

Arachnid commented Nov 4, 2015

Indeed, that's why I'm suggesting embedding additional templates as preferable to duplicating the whole thing. Any errors in the templates will still need correcting in all languages, though.

@OsnaFonz
Copy link
Collaborator Author

if we use template files with a javascript load, we loose the possibility to open the generator on a local machine, because of security reasons. is this ok?
and if this is ok, can we switch to the php-version of mustache? i think mustache is the main reason for the ios-problems (memory usage). and i think server-side rendering can fix this problem.

@Arachnid
Copy link
Collaborator

I'd rather keep it inline if we can. The template data isn't that big that we couldn't embed templates for multiple languages in one page; alternately we could fork the entire page, and put the javascript in its own file (which can be loaded on local FS).

I'm absolutely opposed to writing anything in PHP. :)

@someknave
Copy link
Collaborator

Let me know if it is worth creating some extra tokens, some languages have different plurals and genetive cases so using {{agent}}s, {{agent}}'s, {{owner}}'s, and {{owners}}' would not necessarily work in other languages, these contructions are fairly rare ({{agent}}s is the most common).

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

No branches or pull requests

4 participants