Manual Input

[ronelm2000]

Users should be able to enter translations and new card details manually. This can be done via a new parser which will take in an input file.

The input file shall be in JSON. This allows inputs to be easier to define and do not scale vertically as they can introduce problems when editing manually.

This needs to be well defined before work on it can be started.

[armswar88]

Users should be able to enter translations and new card details manually. This can be done via a new parser which will take in an input file.

The input file shall be in JSON. This allows inputs to be easier to define and do not scale vertically as they can introduce problems when editing manually.

This needs to be well defined before work on it can be started.

For input file specs, may I suggest the following as a first iteration:

• Must be a pure text file (eg. text)
• Cannot be rich text like rtf, doc, etc.
• Must be in an identical format as the HotC format you are already parsing in earlier versions of your product.

By going this way, hoping that you can reuse the same parser that you created for parsing the HotC feed to read in text files. Attached a sample for reference.
sample.txt

Thanks for taking on this project! You're helping people connect in this dark time!

[ronelm2000]

HOTC-style input should be fine I guess. It shouldn't be too difficult for that parser to accept a file. However, a format independent from HOTC is still the ideal format other purposes:

• It allows other contributors to create exporters and/or set editor applications around that format without worrying about how to export a format into HOTC. There's several JSON encoders and editors, all of which are very easy to use.
• HOTC style format may be changed at any time. A new input format would be versioned by me and thus won't be changed unless something happens (like a new mechanic).
• Encore Decks JSON would also work but that JSON format (the one in their Set API) has fields that potential users don't need, like card set limitations, etc.

I still like the idea for HOTC file parser tho, so I will include that as a separate card.