¿ªÔÆÌåÓý

character encoding


 

My table files are all utf-8 (no BOM), and some of them have curly quotes. These quotes show fine in Notepad++, but the Tablesmith results window gives garbage characters associated with a wrong code page.

The right-click menu / encoding submenu shows "Western European (Windows)" followed by "Unicode UTF 8)" with the Unicode menu entry dotted.

Is there a configuration setting for "utf8 and only utf8" in Tablesmith, or is the only work-around to replace the curly quotes in the table files with straight quotes?

--
Erol K. Bayburt
ErolB1@...


 

Hey, Erol -

There's no encoding setting for HTML in TableSmith (never really came up as in issue in the past). I did recall looking at allowing some sort of custom header as an advanced feature, but I just looked through the code and didn't see anything for that, so either it was never implemented or it didn't make it over in the transition from version 4 to 5.

I don't know that your workaround is the only option, but a config setting isn't available. You could maybe try outputting to Text rather than HTML, though I don't know that would make a difference.

Bruce



©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\

On Wednesday, December 2, 2020 7:42 PM, ErolB1 via groups.io <ErolB1@...> wrote:

My table files are all utf-8 (no BOM), and some of them have curly
quotes. These quotes show fine in Notepad++, but the Tablesmith results
window gives garbage characters associated with a wrong code page.

The right-click menu / encoding submenu shows "Western European
(Windows)" followed by "Unicode UTF 8)" with the Unicode menu entry
dotted.

Is there a configuration setting for "utf8 and only utf8" in Tablesmith,
or is the only work-around to replace the curly quotes in the table
files with straight quotes?

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Erol K. Bayburt
ErolB1@...


 

Outputting as text doesn't help.

My guess is that it's a problem in the engine, where it reads in text from the table file as ISO-8859-1/Windows-1252 and so reads (eg) a utf-8 close single quote as ?€? This is then propagated to the output window and the temp htmp file.

Erol K. Bayburt
ErolB1@...

On 12/4/2020 9:23 AM, Bruce Gulke via groups.io wrote:
Hey, Erol -
There's no encoding setting for HTML in TableSmith (never really came up as in issue in the past). I did recall looking at allowing some sort of custom header as an advanced feature, but I just looked through the code and didn't see anything for that, so either it was never implemented or it didn't make it over in the transition from version 4 to 5.
I don't know that your workaround is the only option, but a config setting isn't available. You could maybe try outputting to Text rather than HTML, though I don't know that would make a difference.
Bruce
©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Wednesday, December 2, 2020 7:42 PM, ErolB1 via groups.io <ErolB1@...> wrote:

My table files are all utf-8 (no BOM), and some of them have curly
quotes. These quotes show fine in Notepad++, but the Tablesmith results
window gives garbage characters associated with a wrong code page.

The right-click menu / encoding submenu shows "Western European
(Windows)" followed by "Unicode UTF 8)" with the Unicode menu entry
dotted.

Is there a configuration setting for "utf8 and only utf8" in Tablesmith,
or is the only work-around to replace the curly quotes in the table
files with straight quotes?

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Erol K. Bayburt
ErolB1@...


 

For what it's worth, converting (a copy of) the .tab file from utf8 to 1252 (ansi-latin 1) so that curly quotes show properly when using the 1252 code page gives a table that produces TableSmith output with the curly quotes displayed correctly.

Erol K. Bayburt
ErolB1@...

On 12/4/2020 9:23 AM, Bruce Gulke via groups.io wrote:
Hey, Erol -
There's no encoding setting for HTML in TableSmith (never really came up as in issue in the past). I did recall looking at allowing some sort of custom header as an advanced feature, but I just looked through the code and didn't see anything for that, so either it was never implemented or it didn't make it over in the transition from version 4 to 5.
I don't know that your workaround is the only option, but a config setting isn't available. You could maybe try outputting to Text rather than HTML, though I don't know that would make a difference.
Bruce
©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Wednesday, December 2, 2020 7:42 PM, ErolB1 via groups.io <ErolB1@...> wrote:

My table files are all utf-8 (no BOM), and some of them have curly
quotes. These quotes show fine in Notepad++, but the Tablesmith results
window gives garbage characters associated with a wrong code page.

The right-click menu / encoding submenu shows "Western European
(Windows)" followed by "Unicode UTF 8)" with the Unicode menu entry
dotted.

Is there a configuration setting for "utf8 and only utf8" in Tablesmith,
or is the only work-around to replace the curly quotes in the table
files with straight quotes?

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Erol K. Bayburt
ErolB1@...


 

Good to know!




©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\

On Friday, December 4, 2020 10:27 AM, ErolB1 via groups.io <ErolB1@...> wrote:

For what it's worth, converting (a copy of) the .tab file from utf8 to
1252 (ansi-latin 1) so that curly quotes show properly when using the
1252 code page gives a table that produces TableSmith output with the
curly quotes displayed correctly.

Erol K. Bayburt
ErolB1@...

On 12/4/2020 9:23 AM, Bruce Gulke via groups.io wrote:

Hey, Erol -
There's no encoding setting for HTML in TableSmith (never really came up as in issue in the past). I did recall looking at allowing some sort of custom header as an advanced feature, but I just looked through the code and didn't see anything for that, so either it was never implemented or it didn't make it over in the transition from version 4 to 5.
I don't know that your workaround is the only option, but a config setting isn't available. You could maybe try outputting to Text rather than HTML, though I don't know that would make a difference.
Bruce
©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Wednesday, December 2, 2020 7:42 PM, ErolB1 via groups.io ErolB1@... wrote:

My table files are all utf-8 (no BOM), and some of them have curly
quotes. These quotes show fine in Notepad++, but the Tablesmith results
window gives garbage characters associated with a wrong code page.
The right-click menu / encoding submenu shows "Western European
(Windows)" followed by "Unicode UTF 8)" with the Unicode menu entry
dotted.
Is there a configuration setting for "utf8 and only utf8" in Tablesmith,
or is the only work-around to replace the curly quotes in the table
files with straight quotes?

Erol K. Bayburt
ErolB1@...