Hi @Tut. Just wanted to make sure that you understood that this was not a browser issue I was referring to! In fact the display in the Manager (and other browsers I tried) worked OK. However, the generated pdf file did not work correctly (as I specified).
I suspect at some time Markup was supported, hence dashes turning to bullets.
Markup? Are you perhaps referring to Markdown? Your comment would make more sense if you were. But, of course, there are different versions of Markdown (or its equivalents). And different browsers treat it differently.
HTML: HyperText Markup Language 
Hi @Tut, yeah, my bad, MarkDown was what I meant.
However, I am not referring to a Browser issue. It’s the PDF that fails to work! Does your PDF’s have the correct appearance on the HTML elements I mentioned above?
Simple question, but complex answer. It depends on operating system, browser, etc. As a single example, on a Mac, I don’t see the apple image loaded from that particular URL, just the blue square of death with question mark. But I can load images from elsewhere. Variations in Markdown implementation can change hyphens to bullets, or not. This entire subject is why I am an advocate of simplicity when using Manager. Unless you’re a programming whiz kid, switching machines or program editions can change outcomes. What works in one environment can produce a different result elsewhere. It is very easy to be surprised by an unexpected result.
Well no, it was a simple yes/no answer actually.
I stated that the right align did not work, and you stated that “It worked for me” and you made the same statement about the other 2 issues I pointed out (and of course that does not include the List Items that also failed)
I simply wanted to verify that they were working in the PDF produced, not the display.
So I’m not a whiz kid, and don’t like using terms like expert or guru, however but I have been working with computers since 1982. I’ve worked in banking and financial services industries and even maintained a self managed superfund software product around 12 years ago. I’ve been using Windows since version 2 and Excel since version 1, so I actually understand how most of the smoke and mirrors actually works.
I had a quick look at the Apitron PDF Kit (the 3rdparty addon) and can see that some HTML is never going to work well in Custom Fields due to what the library required to output it. (you would need to parse the field for html and make appropriate calls etc.)
So based on my findings, I think that maybe a list of acceptable html tags should be provided. Maybe a table with 3 columns, showing the tag, expected results for the display vs PDF Output. But that’s just my opinion 
Stay safe… MarkLL
Well, it wasn’t a yes/no answer because I have seen different results under different circumstances. The rest of your post confirms what I said. Your description of your experience qualifies you as a whiz kid in my opinion. Most people would not even understand the things you wrote. Nor would they be able to take appropriate action. But, for what it’s worth, I agree it would be helpful to have a table of HTML syntax that works. But I do not have one.
Hahahah I’m more the opposite these days, slow and old these days, but I do have experience on my side. 
Just to close this out, I found the easiest way to actually get it to work in a PDF is to create a new theme and code it all as a couple of tables. Lists (ul and ol) definitely does not work.
Thanks, interesting that you recommended to use html in custom fields LOL. The amount of text that @ejjaadiargo wanted to add in the end really is better in a custom theme than a custom field anyway.