Where in the docs?

[owen]

Where in the docs does it describe string assignment where the string has quotation marks?

Code: Select all

Print """Hello World"""
Print !"\"Hello World\""

[fxm]

See "Literals" and "Escape Sequences" pages.

[owen]

thanks

[bcohio2001]

Code: Select all

Print Chr(34) + "Hello World" + Chr(34)

[grindstone]

The accepted escape sequences in text are:
\a beep
\b backspace
\f formfeed
\l or \n newline
\r carriage return
\t tab
\unnnn unicode char in hex
\v vertical tab
\nnn ascii char in decimal
\&amphnn ascii char in hex
\&amponnn ascii char in octal
\&ampbnnnnnnnn ascii char in binary
\\ backslash
\(double quote) double quote
\' single quote

Code: Select all

Print !"\&amph23"

output: 'amph23' (should be: '#')

What am I missing?

[St_W]

Code: Select all

Print !"\&amph23"

output: 'amph23' (should be: '#')

What am I missing?

That's a fault in the documentation. & is the HTML code for & so it should read &h23 (instead of &amph23). I'll try to fix it.

[fxm]

That's a fault in the documentation. & is the HTML code for & so it should read &h23 (instead of &amph23). I'll try to fix it.

TblEscapeSequences:
Look at the last 2 rows of the table that are now exploded into 3 lines in the *.chm file.
IMHO, that is why \" was written before \(double quote).

[grindstone]

Thank you.

[St_W]

Look at the last 2 rows of the table that are now exploded into 3 lines in the *.chm file.
IMHO, that is why \" was written before \(double quote).

I feared that something like that happens, but I think that it should be fixed in the CHM rather than worked around on the wiki. I'll try to look into that too.

[fxm]

There is other thing that should be fixed in the CHM.
In the index list, the original "&=" string is displayed as "?":
"? (Concatenate And Assign)" instead of "&= (Concatenate And Assign)"
"Operator ? (Concatenate And Assign)" instead of "Operator &= (Concatenate And Assign)"

[St_W]

There is other thing that should be fixed in the CHM.
In the index list, the original "&=" string is displayed as "?"

Thanks for the hint; I'll look into that too.

[St_W]

Submitted a PR that should fix the encoding issues: https://github.com/freebasic/fbc/pull/49

//edit:
PR has been accepted by dkl and he also noted that some fixes may be necessary (thanks!).
I found only one additional page (to the one mentioned by dkl), which needed to be fixed anyway because they were broken in the online-wiki. The changed pages are:
https://freebasic.net/wiki/wikka.php?wa ... Printusing
https://freebasic.net/wiki/wikka.php?wa ... PgCruntime

If there are any other pages broken by the change please report the errors (or fix them).

From now on please use proper HTML escape sequences in the wiki instead of the previously used workaround with the missing semicolon (e.g. "&" instead of "&amp"). However, in general I'd suggest to avoid the use of HTML escape sequences altogether when possible because of the very limited support in the fbdoc application (which generates the txt/chm/fbhelp help files).

[fxm]

Look at the last 2 rows of the table that are now exploded into 3 lines in the *.chm file.
IMHO, that is why \" was written before \(double quote).

I feared that something like that happens, but I think that it should be fixed in the CHM rather than worked around on the wiki. I'll try to look into that too.

Now, also the similar problem in .chm file for the tables of the two recently updated pages in wiki:
(TblEscapeSequences)
+ KeyPgPrintusing
+ ProPgCruntime

[St_W]

Now, also the similar problem in .chm file for the tables of the two recently updated pages in wiki

The PR has been merged into the master branch now, which should fix:
- the HTML character escaping issues (TblEscapeSequences, KeyPgPrintusing, ProPgCruntime)
- the page title character escaping issues in the CHM (e.g. "Operator &= (Concatenate And Assign)")
- the character encoding issues in the CHM (e.g. on the "Table of ASCII Characters" page)
and some little issues with the documentation build application itself.

[fxm]

Thank you very much.
It's perfect now.