Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

JSON translation file specs #23

Open
9 of 11 tasks
Nico-Duduf opened this issue Mar 14, 2017 · 5 comments
Open
9 of 11 tasks

JSON translation file specs #23

Nico-Duduf opened this issue Mar 14, 2017 · 5 comments
Assignees
Milestone

Comments

@Nico-Duduf
Copy link
Member

Nico-Duduf commented Mar 14, 2017

Data to store:

  • LanguageId (string)
  • LanguageName human-readable full name (string)
  • Dutranslator version
  • Localization objects (Array)

The localization object contains these values:

  • source (string)
  • translation (string)
  • context (string)
  • contextId (int)
  • comment (string)
  • IN Timecode (string hh:mm:ss.ms or hh:mm:ss:f)
  • OUT Timecode (string hh:mm:ss.ms or hh:mm:ss:f)

The translator would find the translations using the original string + (optionnal) contextId
The contextId is necessary in case a unique original string can have two (or more) different translations depending on where it is used

comment and context are strings displayed in the translation editor to help people when translating but not at runtime to translate the strings.

@Nico-Duduf
Copy link
Member Author

Needs to create an example file

@Nico-Duduf Nico-Duduf self-assigned this Mar 14, 2017
@Nico-Duduf Nico-Duduf added this to the 1.0 milestone Mar 14, 2017
@Nico-Duduf
Copy link
Member Author

Nico-Duduf commented Mar 14, 2017

@oktomus
Copy link
Member

oktomus commented Mar 14, 2017

Links not working :/

@Nico-Duduf
Copy link
Member Author

fixed ;)

@Nico-Duduf Nico-Duduf modified the milestones: JSON translation files, 1.0, launch 1.0 Mar 22, 2017
@Nico-Duduf
Copy link
Member Author

Nico-Duduf commented Mar 25, 2017

To enable subtitles import/export, add timecodes (in and out) in the specs

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

No branches or pull requests

2 participants