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

07_beancount_options_reference.html is hard to read #1

Closed
berkes opened this issue Aug 5, 2019 · 3 comments
Closed

07_beancount_options_reference.html is hard to read #1

berkes opened this issue Aug 5, 2019 · 3 comments

Comments

@berkes
Copy link

berkes commented Aug 5, 2019

The formatting is off. It appears to be a combination of the indentation being lost and the paragraphs not being formatted like the source.

https://docs.google.com/document/d/1_-T_BvDtUjj9M7liZMNSkrL8pgC60TGMBlYCiV1e4ZM/edit

afbeelding

And the output:

afbeelding

If configurable in pandoc, an option would be to use a definition-list, DL.
In the current theme, the following HTML:

<dl>
  <dt>option “account_previous_balances” “Opening-Balances"</dt>
  <dd>Leaf name of the equity account used for summarizing previous 
transactions into opening balances.</dd>
</dl>

Shows up as:

afbeelding

@xuhcc
Copy link
Collaborator

xuhcc commented Aug 5, 2019

Unfortunately this google document has very little formatting and it is hard to parse it correctly. For now I just wrapped all paragraphs in code blocks:

c67350f

@berkes
Copy link
Author

berkes commented Aug 6, 2019

For now, I'd say this works fine.

Maybe we can get the upstream google document to change it's markup a little, if we encounter more such issues?
I guess. using a header or even bold lines in the google doc would help pandoc distinguish the outcome.

@berkes berkes closed this as completed Aug 6, 2019
@xuhcc
Copy link
Collaborator

xuhcc commented Aug 6, 2019

Yes, in general I would prefer to amend the original documents instead of comlicating the converter.

In this specific document pandoc sees every single line as a separate paragraph. I think it could be solved by removing unnecessary line breaks in the option descriptions.

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

2 participants