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

Per-language input file #30

Open
vasilisp opened this issue Jan 30, 2017 · 1 comment
Open

Per-language input file #30

vasilisp opened this issue Jan 30, 2017 · 1 comment

Comments

@vasilisp
Copy link

Splitting the input strings across multiple files (one per language) would make maintaining translations much easier. Spell-checking would become practical, diffs/logs would be cleaner, and we wouldn't have to deal with very long lines, tabs, etc.

Imagine how the OS TSV file will look like if we ever add a third language :).

@sagotch
Copy link
Contributor

sagotch commented Jan 30, 2017

Why not, but we then should have both way of input supported. Many files may be way more complicated to maintain. A single key renaming would change three files, same for a key removal. Considering this, diffs/logs would not be that cleaner.

You also have to make sure that everything is defined in all languages which is much more complicated with multiple file (of course, the tool will complain about missing translation but you can see it at the first sight when everything is on the same file.

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

2 participants