Code syntax highlighting

[banana8281982]

So, I am writing (or trying) to write a book about C#. Nothing fancy, just checking if this is something I want to do. But...

I run into a big issue/problem/lack of knowledge. I have some text (H1, paragraphs, nothing fancy) and I want to add some C# code. Now I want to do some syntax highlighting for the distribution of PDF, but it should also look nice-ish for an ePub. And this is where I get stuck.

This is an example of what I want to write:

var query = from student in students
            where student.Age > 18
            orderby student.LastName
            select student;

I have found an example of ebooks that have very nice syntax highlighting, such as blue for the keywords, red for strings, etc. I know this can't be done my the majority of eReaders, but the fact you can also export the book to PDF is a great plus for me.

But what I do, I can't seem to get the highlighting going. Most websites I find tell me to export the text to markdown and then... Magic? Wait for it to turn into a princess? It does somewhat work, but the code is just one line; it misses indents and new lines.
Others suggest to use Prism(.js), which does somewhat work. The text is somewhat shown as I want, but the code that is too long doesn't fall onto the next line, making the reader miss the code.

Can anyone point me in the right direction?

[banana8281982]

Since I can't seem to edit the original post, here a small update:

I found out that I can use pandoc to convert a markdown file to HTML, even with styles. It doesn't look how I want it, but it's a start. When I load the HTML (with the CSS) in a page it looks much better!

But... When I convert it to EPUB and load the EPUB on my ereader, the page is blank!!! When I open the EPUB in a random reader on my pc (WIndows) it looks fine.

So, what am I doing wrong now?

[Karellen]

Originally Posted by banana8281982

So, what am I doing wrong now?

We would really need to see the book, so we can check the code. It's hard to diagnose anything without it.

[Quoth]

Do a version from a wordprocessor for ebook (extra save as docx if not editing on docx, which you shouldn't for LO Writer), then when proofed change the styles, index, footers, headers, page numbers, foot & end notes and syntax highlight (via character styles) for direct export as PDF. Automatic epub to pdf is only a convenience feature.

But I was last writing C++ docs in 1987 and C++ has changed a bit since then and also better authoring/format tools.

Don't use markdown or pandoc. Markdown is for very basic input for a draft version using a plane text editor. I abandoned it years ago.

Also zero direct formatting (glass typewriter syndrome), use styles for everything.