Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: txt output #45

Open
LAfricain opened this issue Nov 10, 2017 · 4 comments
Open

Feature request: txt output #45

LAfricain opened this issue Nov 10, 2017 · 4 comments

Comments

@LAfricain
Copy link

Is possible to have an output file with the txt format?
My concern is to be able to use the application for wiki text like wikipedia or https://doc.ubuntu-fr.org

@crowdagger
Copy link
Owner

crowdagger commented Nov 10, 2017

I thought about adding one, but not sure how it should be done. E.g., if you have a title, a paragraph and a blockquote, should it be displayed as

Title

Paragraph

Blockquote

or e.g.

Title
======

Paragraph 

    Blockquote

? Should the interior of a paragraph be wrapped to e.g. 80 columns, or should the whole content of a paragraph be on a single line, a line break indicating a paragraph break?

I wonder if it wouldn't make more sense to add an output for... Markdown, which could allow using Crowbook for structuring files and some formatting pre-processing (e.g. for non-breaking spaces in french), and then use another program on it (e.g. pandoc which has a huge amount of converters).

@LAfricain
Copy link
Author

LAfricain commented Nov 11, 2017

J'écris French puisque j'ai vu que t'es French.
C'est plutôt du genre:
======Titre======
=====Titre 1=====
====Titre 2====
Paragraphe
etc

C'est bien ça ta question?

? Should the interior of a paragraph be wrapped to e.g. 80 columns, or should the whole content of a paragraph be on a single line, a line break indicating a paragraph break?

Un saut de ligne n'indique pas une rupture de paragraphe mais la balise \ oui. Ou bien carrément une ligne vide.

Markdown, which could allow using Crowbook for structuring files and some formatting pre-processing

C'est surement une excellente idée... Mais je sais pas comment faire. En fait pour te donner plus d'info, je suis admin de la doc ubuntu et on avait soulevé le problème de la ponctuation. Perso je déteste voir un point d'interrogation ou un guillemet en début de ligne et sur Wikipédia c'est une catastrophe! Alors on avait pensé scripter tout ça pour un contrôle automatique des espaces insécables. Mais bon personne n'a de temps pour les détails... Puis j'ai découvert cette application. Et j'ai pensé simplement la proposer comme post-traitement après rédaction ou correction d'une page de doc.
Maintenant si on peut faire mieux tant mieux.
Perso j'y connais pas grand chose… Mais j'aime bien la ponctuation bien faite à la française :)

Edit: en fait je sais pas si c'est une bonne idée la conversion au markdown puisque on travail directement en markdown. Donc je crois que l'idéal serait de passer crowbook directe sur le .txt en markdown?

@Aldian-fr
Copy link

Hi,
Some precisions: The ubuntu french documentation is based on Dokuwiki, which relies on a markup language. But AFAIK the Dokuwiki markup language is different from the markdown standard. As a consequence using Crowbook's post-processing would need to first convert Dokuwiki's markup to markdown.

That said, it seems that some years ago there was a plugin for enabling markdown syntax in Dokuwiki. It seems to be no longer maintained, but is the proof that such conversion is possible.

So I suggest opening another feature request for supporting Dokuwiki's markup as a native input for Crowbook. This would allow to easily export all Dokuwiki based wiki as ebooks (a lot of wikis about open-source software are based on Dokuwiki), so it may be of some use ;)

As for the task of simply auto-correcting mistypes in text files, guess there should be better fitted tools around there.

@crowdagger
Copy link
Owner

While it would be nice to allow to have multiple input formats, I think it's really beyond the scope of this project (or at least my skills, after all I didn't even write the Markdown parser, it's a library I just use ^^).

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

No branches or pull requests

3 participants