Skip to content

< and > get replaced by html entities #61

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

Closed
Vampire opened this issue Mar 12, 2024 · 4 comments
Closed

< and > get replaced by html entities #61

Vampire opened this issue Mar 12, 2024 · 4 comments

Comments

@Vampire
Copy link

Vampire commented Mar 12, 2024

This function can be used on a `Configuration` or `Provider` thereof to get a
`Provider<List<File>>` with the platform-dependent artifacts for the
operating system given as argument.

is translated to

This function can be used on a `Configuration` or `Provider` thereof to get a
`Provider&lt;List&lt;File&gt;&gt;` with the platform-dependent artifacts for the
operating system given as argument.

This makes the sources harder readable and seems to be unnecessary.
If there are cases where it is necessary, it would be nice if only those would be transformed.

@Vampire
Copy link
Author

Vampire commented Mar 12, 2024

https://github.com/asciidoctor/kramdown-asciidoc even does it the other way around.
If it gets as input the Markdown

&lt;undefined&gt;

a &#124; b

a &amp; b

it transforms it to the AsciiDoc

<undefined>

a | b

a & b

which seems to be nicer.

@bodiam
Copy link
Collaborator

bodiam commented Mar 12, 2024

Thanks for your feedback @Vampire . Are you planning on using this library or were you just comparing the outputs?

@Vampire
Copy link
Author

Vampire commented Mar 12, 2024

I had a readme in md that I wanted to port to adoc, mainly to get a nice ToC rendered easily.
I probably plan to do the same with some others too.

I asked Dan what he recommends for that and he recommended his kramdown-asciidoc.

After doing it with that, I learned, that the IntelliJ AsciiDoc plugin has also such a functionality included,
so did the conversion with that functionality again and looked at the differences which partly are bugs and partly just quirks.

I then looked up what the plugin uses, found this project, and create the 8 issues.
For now I'm through with the differences. :-)

bodiam added a commit that referenced this issue Apr 11, 2024
@bodiam
Copy link
Collaborator

bodiam commented Apr 11, 2024

I've fixed the original issue by no longer escaping the data. I didn't implement the second suggestion.

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