Hi, Here are excerpts from Edsharp documentation involving unicode characters. The documentation seems to indicate that there is some support in Edsharp for unicode. --- beginning of quoted material from Edsharp documentation --- The Yield Encoding command, Alt+Shift+Y, may be used to convert all or selected text according to a particular character encoding. If text from a file or the clipboard appears to be rendered improperly in EdSharp, you can tell it to base its interpretation on a different encoding: ASCII, Latin 1, UTF-7, UTF-8, UTF-16, UTF-32, or another encoding that you pick from a list of over 100 available. You can also choose a conversion where the Unicode number of each character is put on a separate line. This may be used to identify non-printing characters in the document. The command replaces all or selected text, so put a copy in a new document window if you want to retain the original. F2 prompts for a character to insert based on its numeric value in the Unicode character set. The number should have four hex digits (base 16). This command is useful for inputting a character that does not have a corresponding keystroke. You can specify a decimal (base 10) number instead by preceding it with the letter d. For example, the ellipses symbol (...) may be specified either in hex as 2026 or in decimal as d8230. When saving text to a file, EdSharp checks whether any character has a Unicode number greater than 255, which means that more than one byte is needed to represent it. If so, the file is saved with a UTF-8 encoding, the most common form of Unicode for storing files on disk. Otherwise, the default encoding of the computer is used, e.g., Latin 1. Alt+Shift+E exports a file to another format. Built-in options include ASCII format (characters with ANSI codes above 127 are removed), Mac format (line break is \r), and Unix format (line break is \n). Via Microsoft Word converters, additional formats include .doc, .htm, .rtf, and .xml. Other converters may be configured by editing the Export section through the Manual Options command, Alt+Shift+M. The syntax is like that in the Import section (explained elsewhere). The Other option lets you pick a character encoding for the target file from a list of over 100 available. The YieldEncoding setting determines the character encoding EdSharp will use when opeing a file from disk. EdSharp ignores this setting if the file has a .rtf extension indicating rich text format, or has an initial byte order mark (BOM) indicating Unicode format (e.g., UTF-8 or UTF-16). An encoding may be indicated by either its name or number. A list of those available may be found by choosing the Other option in the Yield Encoding command, Alt+Shift+Y, or Export Format command, Alt+Shift+E. If no YieldEncoding setting is configured, EdSharp uses the default encoding configured in the regional settings applet of Windows Control Panel. Typically, the setting is Western European. Use the Status command, Alt+Z, pressed twice in order to check the encoding that EdSharp used to open the current document. EdSharp will save the document with the same encoding. --- end of quotes from Edsharp documentation --- Jet (jeffrey Thompson) From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On Behalf Of Zahari Yurukov Sent: Tuesday, May 06, 2014 11:31 AM To: pythonvis@xxxxxxxxxxxxx Subject: [pythonvis] Re: Text editors Hi, NVDA can report indentation in any editor, and as I can recall JAWS has this option too. Regarding the translation - may be you are right: it will be in separate files, so it might not be a problem. But if you want to use nonascii characters in your code or non latin characters - it is 100% better to use unicode than some other encoding. If you open a file with wrong encoding and save it in another encoding you will break the text. The Unicode encoding is getting you out of this encoding mess. Of course everyone is free to use whichever editor he/she likes. Best wishes, Zahari На 6.05.2014 17:46, Richard Dinger написа: I have the same question. Richard From: Jeffrey Turner <mailto:jturner522@xxxxxxxxx> Sent: Tuesday, May 06, 2014 7:02 AM To: pythonvis@xxxxxxxxxxxxx Subject: [pythonvis] Re: Text editors Hello Zahari, Thank you for your comments about text editors. Can you clarify one point for me? As beginners (some of us Jaws users), the EdSharp editor has some significant advantages for us, like announcing indent levels automatically as we arrow up and down through the lines of code. I can see the drawback of not having Unicode included, but as a beginner, I have no aspiration to have anything I write translated into other languages. In the event that this is a requirement someday down the line though, what is keeping someone from taking my code, and editing it using an editor that does support Unicode? Why would this be any different from someone taking a *.txt file created in Notepad and modifying it using Word or any other editor? It seems like the lack of Unicode support is not relevant to the needs of many of us. Am I missing something here? JDog From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On Behalf Of Zahari Yurukov Sent: Monday, May 05, 2014 9:07 PM To: pythonvis@xxxxxxxxxxxxx Subject: [pythonvis] Re: Text editors Hi, I very much appreciate this initiative and I'm reading your letters with big interest. I have some experiance with PHP, and very little knowledge in Python, but I want to learn and to share that what I've learned with others. I think that Unicode support is essential for a text editor these days. Even if you are an English speaker, you probably will want your program to be translated in other languages some day. And I can assure you, that dealing with different encodings is a hell. Unicode contains not only different alphabets, but many other symbols, too. So you would like your program to be written in unicode, and that's why you need a unicode editor. It is very disturbing that the developer of EdSharp refuses to include unicode support. Also, wouldn't it be harder for a beginner to remember hundrets of keystrokes, instead of using standard text navigation and manipulation commands? I personally prefer Notepad++ for everything, but I'm NVDA user. For JAWS users, why don't you try UltraEdit. I havn't use JAWS for many years now, but I think it should be accessible, though I can't guarantee (just an idea). P.S. M$ Notepad is the worst text editor ever - please don't use it, grin. Best wishes, Zahari На 27.04.2014 17:30, Richard Dinger написа: You should use a text editor to write programs. Word processing programs like M$ Word or Wordpad do not work well because they include extra display and format information that will only confuse the Python compiler. This is true for any programming language, not just Python. There is an endless debate among programmers about which is the best language and another endless debate over which is the best text editor. You must select the editor you will use, based on your own preferences. Here is a list of text editors that I have seen recommended by visually impaired programmers: - M$ Notepad (bare bones editor comes with windows) - Notepad++ (free download many advanced features) - Notepad2 (free download many advanced features) - Textpad (not free many advanced features) - EdSharp (free download many advanced features very blind friendly) The Notepad editor that comes with windows is bare bones, but I used it for many years just because it was simple and easy to use. One drawback is that Notepad is not “language aware” , that is it has no Python specific features or the ability to run the script being edited. I think the others listed above all have some language specific features, but I am not knowledgeable enough to list them here. Read through their respective websites to get more details. The EdSharp editor is recommended on our web page, but is not required. EdSharp can be configured for Python and can run scripts from within the editor. There are several Python specific features that will make your study of Python a little easier. Richard