the file may be saved as Western (ISO Latin 1), but when opening in jEdit, the information at the bottom of the window persistently shows Mac Roman, and the special characters are screwed. (This appears to happen whether the jEdit default file preference is set to Western (ISO Latin 1) or not.)

You MUST the character set the file was saved in with the default character set for jEdit. There is no heuristic way for an editor to figure out the difference between MacRoman and 8859-1 just by looking at the file contents. They are both 256 byte extended Roman character sets. How could it know?

If a file was saved in MacRoman, you have to open it in MacRoman mode, change the buffer encoding to 8859-15 (see next paragraph as to why), then save it. The great thing about jEdit is that you can record this whole routine as a macro, assign it to a key, and quickly apply it to many files. Or you could extend the macro yourself to apply it to a whole directory automatically. Try doing that in BBEdit...

You are actually better off using 8859-15 as the default character encoding. It is the same as 8859-1, but replaces some little-used characters with some missing European language characters. More importantly, it has an official place for the Euro symbol, and 4D is using that encoding it seems when converting to ISO.


As to the whole debate about BBEdit vs. jEdit: from list members' points of view, what are the convincing benefits of switching editors, (excluding syntax highlighting)?

In no particular order:

macros
project viewer plugin
code folding
syntax highlighting
XML plugin

You should not underestimate the importance of syntax highlighting. It is easier to program with syntax highlighting because you can visually parse your code more easily, and you get instant visual feedback as to the syntactic correctness of what you are writing. Also, it does auto-indentation after control structures. The overall experience is much better than without.

The project viewer plugin is fantastic, it saves you a lot of trips to the open dialog. Code folding is great at times. The XML plugin is great when writing HTML. It does tag balancing and stuff like that.

I used BBEdit for years with Active4D, and once I got used to jEdit I never looked back (at BBEdit) and never missed it. Give it a chance.

Regards,

   Aparajita
   www.aparajitaworld.com

   "If you dare to fail, you are bound to succeed."
   - Sri Chinmoy   |   www.srichinmoylibrary.com


_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/

Reply via email to