Windows Client Runtime Settings

[Steve]

Another team at my work wishes to connect to our Ingres installation (Ingres 11 running upon Solaris SPARC) from SQL Server using ODBC. They have installed the Windows Client Runtime on their SQL Server box. They wish to only query our Ingres database.

II_CHARSETCR is set to the Windows default of WIN1252. However, I am somewhat confused if this is OK or should it be changed to match the Ingres server setting of ISO88591 (the UNIX default)?

Thanks
Steve

[Adrian Williamson]

Hi,

https://en.wikipedia.org/wiki/Windows-1252

"It is very common to mislabel Windows-1252 text with the charset label ISO-8859-1. A common result was that all the quotes and
apostrophes (produced by "smart quotes" in word-processing software) were replaced with question marks or boxes on non-Windows
operating systems, making text difficult to read. Most modern web browsers and e-mail clients treat the media type charset ISO-8859-1
as Windows-1252 to accommodate such mislabeling. This is now standard behavior in the HTML5 specification, which requires
that documents advertised as ISO-8859-1 actually be parsed with the Windows-1252 encoding.[5]"

So 1252 is a superset of ISO88591- so they should be OK reading your data, but if they started putting text data in then it might look odd on Solaris?

However when it comes to issues around getting £ or € symbols to appear, I am always prepared to be surprised.

We have had issues in the past with non-breaking white space, control characters put in place to affect paragraph alignment - copy and paste issues from Word into OpenROAD into Ingres.

Cheers

Adrian

_______________________________________________
Info-ingres mailing list
Info-...@lists.planetingres.org
https://lists.planetingres.org/mailman/listinfo/info-ingres