Dutch_Master wrote:Re-install the affected font? That is, if you're sure that font should have the missing symbol in the first place, if the symbol wasn't defined in the font I'm not surprised it doesn't show up Change to a different font to see where the issue actually is: if the missing symbol turns up, there's a problem with the original font.
johnhudson wrote:This is guesswork but the question is: what does postgres actually do?
AFAIK currency formats are not part of SQL; so, even if you CAST() a number as a currency and postgres displays it correctly, it may, for compatibility reasons, not be exported as such.
Alternatively, you may need to investigate the import options of the program that receives the data and match the postgres output to that - for example, currency symbols may not be accepted as part of numeric data.
johnhudson wrote:Then is there an encoding problem, e.g. utf8 to unicode 16 or something like that?
johnhudson wrote:ADO.NET is a Microsoft product and probably uses Unicode 16. That is why I wondered whether the problem is UTF8 to Unicode 16. But it may use a different encoding which would explain the problem.
Unicode 16 uses 2 bytes for every character whereas UTF8 uses a variable number of bytes depending on position in the sequence.
(I am surprised that you are getting the problem but this is the only explanation I can think of in the light of the information you have shared.)
Users browsing this forum: No registered users and 1 guest