More unicode... but this might be doable fairly easily.
Posted: Sun Oct 12, 2008 8:15 pm
I've read a lot of the things on the forum dealing with unicode because I am dealing with a Japanese site that is using its English sister site's code.
I've managed to figure out enough that I'm not having too much trouble getting those Japanese characters in there, but I'm still having issues with existing files.
This is not as much a bug report as a description as to what happens (I'm still not sure if it's stupid program or stupid programmer
), the enhancement I'm suggesting is how TextPad handles this particular error.
Basically, what happens is that no matter how I set the script and font, whether in the class or for that individual document, it is still reverting to a non-unicode font when I re-open it, and I get the message "Warning: "file" contains characters that do not exist in..."
That might be me missing a setting, but despite my changing settings and then saving the file, and setting the font to a unicode one on the class, it always reverts to the default font.
If I say yes and open it, it replaces all my carefully pasted Japanese characters and I have to do the job all over again. If I say no, I can't edit it.
Right now, I handle it by opening the file, updating the font settings, and then I download the correct file from the server and overwrite it--when it updates the live file, it's got the correct settings and characters.
What would be really useful, though is to offer the option to "ignore" the character set and don't replace those characters (which would preserve them while you adjusted the font settings), or even better: "Warning: "file" contains characters that do not exist in your selected font. Choose a different font?" and then when you click yes, it pops open the font selection screen."
Thanks.
I've managed to figure out enough that I'm not having too much trouble getting those Japanese characters in there, but I'm still having issues with existing files.
This is not as much a bug report as a description as to what happens (I'm still not sure if it's stupid program or stupid programmer
), the enhancement I'm suggesting is how TextPad handles this particular error.Basically, what happens is that no matter how I set the script and font, whether in the class or for that individual document, it is still reverting to a non-unicode font when I re-open it, and I get the message "Warning: "file" contains characters that do not exist in..."
That might be me missing a setting, but despite my changing settings and then saving the file, and setting the font to a unicode one on the class, it always reverts to the default font.
If I say yes and open it, it replaces all my carefully pasted Japanese characters and I have to do the job all over again. If I say no, I can't edit it.
Right now, I handle it by opening the file, updating the font settings, and then I download the correct file from the server and overwrite it--when it updates the live file, it's got the correct settings and characters.
What would be really useful, though is to offer the option to "ignore" the character set and don't replace those characters (which would preserve them while you adjusted the font settings), or even better: "Warning: "file" contains characters that do not exist in your selected font. Choose a different font?" and then when you click yes, it pops open the font selection screen."
Thanks.