I don't know what's happening (I have zero experience with LazReport) but by the error it sounds like the problem isn't markup in general but the specific text "[?]".
Can it be that LazReport expects to have a field name specified in that way i.e. "[fieldname]"? If so, there must be a way to scape it somehow.
...I not know and make try suggest.
There doesn't seem to be any way to escape it if you want it to be taken literally but I've only skimed the text.
...
<Title>
<Artist>
<Key: ['[?]']>
If I have to escape every character that is not allowed... then I will need a list of them all.
a "!" is not allowed either, so I need to know what all of them are.
If I have to escape every character that is not allowed... then I will need a list of them all.
a "!" is not allowed either, so I need to know what all of them are.
The problem is the square brackets [ and ]. The square-brackets are used to insert variables and datafields but apparently (from the answers above) you can use them also to add literals, so when you have in your text p.e. [Dd] you have to replace it with ['[Dd]'].
It's not so difficult: just replace every instance of "[" by "['[' and instances of "]" with "]']" before printing and back after printing.
That should do the trick :)
I am still needing the list of all excluded characters from the LAZ Report
I am still needing the list of all excluded characters from the LAZ Report
What do you mean by "excluded characters"? You mean that if you add, for example, "sacre bleu!!!" LazReport will silently delete the "!"? Or that adding this question it deletes the "?"?
I find that hard to believe but, as I said above, I have zero experience with it ...
In any case, it shouldn't be difficult to ascertain: prepare a text with all characters and send it to a report to see which characters are silently dropped. Only, take care to exclude the square brackets from it: you already know those are special.
What do you mean by "excluded characters"? You mean that if you add, for example, "sacre bleu!!!" LazReport will silently delete the "!"? Or that adding this question it deletes the "?"?
All I need it a list of all the characters that LAZ Reports hides from the printed page, so I know which characters I am supposed to escape in code.
What do you mean by "excluded characters"? You mean that if you add, for example, "sacre bleu!!!" LazReport will silently delete the "!"? Or that adding this question it deletes the "?"?
All I need it a list of all the characters that LAZ Reports hides from the printed page, so I know which characters I am supposed to escape in code.
Yeah, I got that, but you don't answer my question: Do you mean LazReports eats-up some characters wherever they are and not just when they are between square brackets?
Correct...as I mentioned above it slao ate the "!" character which is not on between "[]"'s
OK, let me investigate a little ... though it will be mostly googling around: I don't have LazReport installed (never use it).Is not need install. maybe read 15 second ? :-X
OK, let me investigate a little ... though it will be mostly googling around: I don't have LazReport installed (never use it).Is not need install. maybe read 15 second ? :-X
Now serious: It seems the problem is that other characters beyond the square brackets are also treated as "special". Pixelink needs to know what those are to, if needed, scape them (probably by replacing them with ["somechar"].
If you have LazReport installed or the sources at hand, maybe you could look into that?
That's where the parts enclosed in square brackets are treated. We already knew that. Maybe read 20 seconds? ;):D
Now serious: It seems the problem is that other characters beyond the square brackets are also treated as "special". Pixelink needs to know what those are to, if needed, scape them (probably by replacing them with ["somechar"].Me serious.
If you have LazReport installed or the sources at hand, maybe you could look into that?Literal = literal and no literal= parse special and have function and calculate.
....Have same answer. Make literal.
You never know what characters a user may insert into any string.
...