I think the bug belongs to macOS, but it’s just an opinion. Judge by yourself.
I place text in file names (after the page number) and in some cases I placed text inside < h1 >< /h1 > tags for later work.
NOTA: the < h1 >< /h1 > tags (read it without the spaces) is skipped by this software !
At Xojo project run time, I generate an html document that is displayed using an HTMLViewer. What was my surprise when the text inside the < h1 >< /h1 > tags AND AFTER ! appears taller. I looked at the line with attention and noted the end tag: <:h1>.
It is impossible to use the ‘:’ character in a file name under macOS, but I go there to check.
In fact, it is at read time (I think) that the change have been done.
Not a nuisance as the < h1 >< /h1 > tags have to be removed in some hours and is a memory recall, not part of the work process. I can use a sheet of paper to do that (or something else).
The prohibition of forward slash in a Unix/Linux filename is documented.
On Mac, the problem is that Linux may accept the colon, but since the finder uses it internally, it shows it as -. Yet, the original Unix filename still contains the colon.
Personally, I would avoid both forward slash and colon altogether. Issue is, you can bet users will occasionally insist on using these characters and complain it is a bug.
I found an entry in Apple documentation statin “Some third party Applications does not like slash.” (bad translation from French).
So, the “fault” is Xojo.
Not a problem for me since this was a simple reminder that will be (or is already) removed at project beta stage.
Extract from the Apple document (the title of that document is: “Renommer des fichiers, dossiers et disques”):
