Feature Request #5315

"Upload language file"

Added by planetmaker over 6 years ago. Updated about 6 years ago.

Status:NewStart date:2013-03-18
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


The "upload language file" could be made available at two additional locations where it would need verification that the actual langID is the same as the existing language. That would also prevent to accidentially overwrite a translation of another language with a bad upload.

  • When reviewing a language as a whole, one can offer to update / upload a new version for that specific language from that sub-page as well.
  • In the project overview in the line for the actual language.


#1 Updated by Alberth over 6 years ago

I am not sure using language files as update mechanism is the right way to go; I see them as the interface between newgrf author and eints, not as medium between translators and and the web service.

iirc in the default rights setup, only admins and project owners can upload a language file.

#2 Updated by Alberth about 6 years ago


09:25:30  <Alberth> I was thinking to generate a file with "some set" of strings (eg all, or outdated, or whatever), with for each string, the current base, the current translation, and an empty new translation
09:25:57  <planetmaker> Hm. And offering that to translators?
09:26:10  <Alberth> translators can fill in the new translation entry, and send it back

Also available in: Atom PDF