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

Questions about html block and inline formatting #51

Open
rgb-24bit opened this issue Mar 31, 2018 · 6 comments
Open

Questions about html block and inline formatting #51

rgb-24bit opened this issue Mar 31, 2018 · 6 comments

Comments

@rgb-24bit
Copy link

The html block of org 9.0 was modified from #+BEGIN_HTML to #+BEGIN_EXPORT html, which seems to make it impossible to export the html block properly when using org 9.0.

If the symbol of the inline style is close to the quotation mark, it cannot be exported properly:

~'test'~

The result of hope: 'test'

The results obtained: ~'test'~

@wallyqs
Copy link
Owner

wallyqs commented Mar 31, 2018

BEGIN_EXPORT not yet supported, and the issue with inline sounds like a bug in the regex in the parser for those..

@melioratus
Copy link

@rgb-24bit

The ~'test'~ rendering issue is very similar to issue #48. I posted a workaround which you might find useful.

@rgb-24bit
Copy link
Author

@melioratus I tried it, this is a solution, thank you

@alphapapa
Copy link

alphapapa commented Sep 4, 2018

Support for the new #+BEGIN_EXPORT blocks would be very welcome. :)

@melioratus Thank you, this also solved a problem for me. When exporting my README.org file to info with ox-texinfo, a #+BEGIN_HTML block gave an error, which prevented the texinfo file from being converted to the info file (an invalid texinfo command, @HTMLnil was output into the texinfo file). Switching to #+BEGIN_EXPORT html fixed that problem, but then the HTML wasn't rendered by GitHub's Org renderer (this project). Using #+HTML fixed it: Org 9 exports the texinfo file correctly, and GitHub renders the HTML correctly.

@Harag
Copy link

Harag commented May 10, 2021

Since this is still open, just checking to see if there is anything in the pipeline to support #+BEGIN_EXPORT options yet?

@maxnikulin
Copy link

Concerning #+begin_export, an older issue bdewey#73 and a pull request bdewey#75 exist.

For a while to have to have a file compatible with org-ruby and Emacs Org mode instead of using a block, each line should be prepended with

#+html: <strong>workaround</strong>

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

6 participants