One question is whats should happen to mapping.json. Separating out the common info just requires making a common JSON file with only that info and the card tag, and leaving the card name/set name/description/extra in the language-specific files. That said, I do agree that tags for both should be separate from printed name strings. Card names are mostly already a unique identifier, with only revisions requiring added tagging. I also think we're not that far from doing this. Plus, it would be easier to error check what is missing in translations. I do agree in principle, and note that not only future sets but also translations would greatly benefit from the increased sharing and thus error checking and consistency that the English version has received. And until someone translates it, and adds its data, it does not even show up. It will also make it more obvious that a translation is needed. Lets say a new card is added, then all languages at least get the divider, even if it temporarily has the primary language. If there is any structural changes/fixes, it goes to all languages immediately. As a backup, the primary language can be used if a card or set has not been translated.These are generally: name, description, and extra. Using the card identifiers, language files would only need have the text elements unique for that language.Data that is common across all languages could be separated out and put in one place, or stored in only one primary language file.Likewise sets would have a unique identifier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |