We should refactor the current translate_code and translate_all into specific end target writers to improve this code base. It is currently confusing to have all the states included in a single writer depending on a wide set of options.
I propose:
translate_code as the base object used to write notebooks that just contain code blocks
translate_ipynb for as the primary for producing ipynb files that has an emphasis on readability and supports markdown as much as possible
translate_html for writing ipynb files used in the production of the website and favours using html objects in the notebooks
translate_pdf for writing ipynb files used in the production of pdf files.
mmcky
commented
4 years ago
We should refactor the current
translate_codeandtranslate_allinto specific end target writers to improve this code base. It is currently confusing to have all the states included in a single writer depending on a wide set of options.I propose:
translate_codeas the base object used to write notebooks that just contain code blockstranslate_ipynbfor as the primary for producingipynbfiles that has an emphasis on readability and supports markdown as much as possibletranslate_htmlfor writingipynbfiles used in the production of the website and favours usinghtmlobjects in the notebookstranslate_pdffor writingipynbfiles used in the production ofpdffiles.