Hi,
One feature that seems to be missing in Jext is to specify the encoding of a file on opening or saving it.
I know there is a setting for the default file encoding, but this isn't very useful if you need to change the encoding of a file.
In my case, a friend needs to save input files for a program in UTF-8. Her Mac is configured to use some other encoding (either some Mac encoding or a Chinese encoding...I haven't figured that out).
When opening a file, it would be good for the user to be able to specify an encoding other than the default, then specify a different encoding when saving it. Jext should actually perform the conversion (and warn when the conversion is impossible, of course.)
It seems there aren't many programs on the Mac that can do such a thing right now, so this would represent a niche on that platform. This capability is particularly important when writing HTML in languages other than English.
Logged In: YES
user_id=1317809
Originator: NO
I agree with you Stevan. I think the encoding option would be more useful, on a file by file basis, than the Unix/Mac/DOS option currently available (bottom left).
A desirable behavior could be:
- when first opening a file, display it using the default encoding specified in global Editor properties
- display the list of available encodings in a drop-down replacing, or on the side of Unix/Mac/DOS drop-down list. The default encoding is selected until user changes something; for some file types (XML) the actual encoding of the file can be detected from the file content and used instead of default encoding
- when the user selects a different encoding, text display is refreshed, using the chosen encoding (this is not a conversion of the underlying data from one encoding to the other)
- on saving, data is saved using selected encoding, for example default or detected encoding if the user did not select a different one