Replies: 4 comments 2 replies
-
So do I understand this correctly that you only want to export this? If you find things that aren't correct, you would go back into godot and change them there? I'm asking because I have thought about a good way to import/export the text data of timeline into a table or text format like .csv, because that could be useful for proofreading or even translating. But that would only be useful if you could import it back into dialogic. An export-only solution should be relatively easy. Would you want all data to go into a single file or what? How should it deal with definitions in text? Should they keep their [MyDefinition] form or be replaced with the default value of the definition? |
Beta Was this translation helpful? Give feedback.
-
I've done a little more work on the desired output format - cleaned it up further. Please see the attachment: |
Beta Was this translation helpful? Give feedback.
-
How is this going on in 2024? I just found this page on localization: https://docs.dialogic.pro/translation.html that seems to hint that CSV is now supported (although not JSON, and above all gettext, see #1874, for better versioning and localization tool support). I'd need this to use Dialogic on any narrative project bigger than a jam, would you say that the current system of Update CSV files + Collect translations is good enough to start working on long dialogues and have them reviewed, proofread externally (I'm also thinking about automated spellchecks or even Google Doc style ML-based suggestions), translated then reinjected into Godot assets? I may try some translation of our jam game post-jam to see how it fares. |
Beta Was this translation helpful? Give feedback.
-
I will close this discussion as it has been quite some years. |
Beta Was this translation helpful? Give feedback.
-
As a Content Creator, I would like to be able to export the definition of the characters and timelines for the purpose of review & [cross-]referencing one timeline against another for comparison/consistency purposes.
I understand that each timeline is it's own JSON file, and that there is a higher-level JSON file which identifies all the individual timelines.
However, as a Content Creator, I don't want to have to manually:
I've attached an initial DRAFT sample text layout for discussion purposes. It PURPOSELY excludes the unnecessary 'id', 'entity relationship', and 'animation-related' fields.
Proposed Export Format.txt
A format like this will be much easier to work with in other tools than the current JSON format.
Beta Was this translation helpful? Give feedback.
All reactions