Member 16359559 wrote:
displayed correctly under html in Debian 9, but not later.
I would start with the assumptions in there. A stored character has a binary representation. There is no way you can see a character until it is 'translated' into a viewer. Doesn't matter what the viewer is it still must do that translation. And sometimes there is more than one translation in the pipeline (for example database to driver, to a 'string', then to 'html', then to a browser.)
Member 16359559 wrote:
Greek alphabet
That also is an assumption. There is a character set, a binary representation, which is used for a 'language'. It will have a specific name. So you really need to determine what that is. Then the steps First extract the binary data from the database. Probably test data. Determine if the form is correct. That is does the binary value (hex or binary) match the character set. Note that if you attempt this by displaying a 'character' then you are not doing it correctly. If the binary value is not correct for the character set then nothing you can do in the code will fix that. Second step determine the pipeline from binary to display. This does include the driver between the whatever application/code that reads the database itself. For each step you must determine whether the binary value retains its original correct value. If you find a step where it is wrong then you have found where the problem is. You should also look for a different way to view the data besides html and a browser. Even just initially that might be the easiest way to determine if those are the problem.
