Topic: Question about VEDIT.INI Charset parameter (1 of 15), Read 36 times Conf: Installation, Configuration From: Peter Rejto Date: Thursday, July 28, 2011 12:59 PM Hi, After changing the Charset=AMSI or OEM parameter via the {View, Font} menu command, the Vedit.ini file does not update this parameter. Is this peculiar to my installation ? To be sure, this is not a high priority item for me, since I already have a short macro displaying the "actual" Charset parameter. I just thought no harm done asking. Thanks as always, -peter

Topic: Re: Question about VEDIT.INI Charset parameter (2 of 15), Read 31 times Conf: Installation, Configuration From: Ted Green Date: Thursday, July 28, 2011 10:01 PM ----- Original Message ----- > From: "peter rejto" ( rejto@... ) Hi, > > After changing the Charset=AMSI or OEM parameter via the {View, Font} > menu command, the Vedit.ini file does not update this parameter. > > Is this peculiar to my installation ? > > To be sure, this is not a high priority item for me, since I > already have a short macro displaying the "actual" Charset parameter. > > I just thought no harm done asking. The "Typeface=" generally selects the desired font by name. The font will then tell Windows whether it is an OEM or ANSI font. In the rare case a font is implemented with two character sets, the "Charset=" field will select the desired one. However, I don't know if any current font is supplied that way. Based on the sizes, weights and styles available in the selected font, the "Height=", "Weight=" and "Italic=" will select the CLOSEST choice, IF POSSIBLE. The issue of fonts and these parameters in the vedit.ini file are more complex than I want to get into. You are welcome to experiment, but you would need to read Windows API programming books to understand what is really happening. Ted.

Topic: Re: Question about VEDIT.INI Charset parameter (3 of 15), Read 32 times Conf: Installation, Configuration From: Pauli Lindgren Date: Friday, July 29, 2011 05:11 AM On 7/28/2011 10:01:27 PM, Ted Green wrote: >----- Original Message ----- >> From: "peter rejto" ( rejto@... ) >> >> After changing the Charset=AMSI or OEM parameter via the {View, Font} >> menu command, the Vedit.ini file does not update this parameter. Peter, The vedit.ini file is only updated when you close Vedit. If you open vedit.ini file in Vedit after you changed the font, it has not yet been updated. You need to close and re-open Vedit to see the changes. > > The "Typeface=" generally > selects the desired font by > name. The font will then tell > Windows whether it is an OEM > or ANSI font. In the rare case > a font is implemented with two > character sets, the "Charset=" > field will select the desired > one. However, I don't know if > any current font is supplied > that way. Ted, Does the "Charset=" option refer to the "Script" field in the Font dialog? For example, I have a font called "DejaVu Sans Mono". This font has two script options: "Western" and "Greek". If I select "Western", vedit.ini contains line "Charset=ANSI". If I select "Greek", the "Charset=" option is empty (nothing after '='). After selecting "Greek", the Greek characters are visible. However, next time I start Vedit, the "Script" field is changed back to "Western", and after closing Vedit, vedit.ini contains "Charset=ANSI" again. It appears that Vedit does not accept any other choice than ANSI or OEM. I think it would be good idea to accept any script option. This would be the first step in making Vedit usable for other languages (Greek, Russian etc.). -- Pauli

Topic: Re: Question about VEDIT.INI Charset parameter (4 of 15), Read 28 times Conf: Installation, Configuration From: Peter Rejto Date: Friday, July 29, 2011 09:12 AM On 7/29/2011 5:11:55 AM, Pauli Lindgren wrote: >On 7/28/2011 10:01:27 PM, Ted Green >wrote: >>----- Original Message ----- >It appears that Vedit does not accept >any other choice than ANSI or OEM. I >think it would be good idea to accept >any script option. This would be the >first step in making Vedit usable for >other languages (Greek, Russian etc.). > >-- >Pauli Aha, (Greek, Russian etc.) would be more difficult then French, German and Hungarian. At least, I could properly display the Hungarian accents from the WinEdt Hungarian dictionary file using Vedit's ASCII character set. I sure was glad to see that ! So, for me the good news is that the special case in which I am interested in is much simpler than the general case. I also consider Ted's reply about the complicity of the general case as good news. May be, you would consider looking at LaTeX. I remember that Fritz tried hard to interest Christian in LaTeX, but no success. Thanks as always, -peter

Topic: Re: Question about VEDIT.INI Charset parameter (5 of 15), Read 31 times Conf: Installation, Configuration From: Ted Green Date: Friday, July 29, 2011 09:28 AM ----- Original Message ----- > From: "Pauli Lindgren" ( pauli0212@... ) On 7/28/2011 10:01:27 > > Peter, > > The vedit.ini file is only updated when you close Vedit. > > If you open vedit.ini file in Vedit after you changed the font, it > has not yet been updated. You need to close and re-open Vedit to see > the changes. Thanks Pauli, I forgot to mention that. To edit the vedit.ini file, you need to use e.g. Notepad or the DOS version of VEDIT. Ted.

Topic: Re: Question about VEDIT.INI Charset parameter (6 of 15), Read 28 times Conf: Installation, Configuration From: Peter Rejto Date: Friday, July 29, 2011 03:08 PM On 7/29/2011 9:28:41 AM, Ted Green wrote: >----- Original Message ----- >> From: "Pauli Lindgren" ( pauli0212@... ) On 7/28/2011 10:01:27 >> >> Peter, >> >> The vedit.ini file is only updated when you close Vedit. >> >> If you open vedit.ini file in Vedit after you changed the font, it >> has not yet been updated. You need to close and re-open Vedit to see >> the changes. > >Thanks Pauli, I forgot to >mention that. >To edit the vedit.ini file, >you need to use e.g. Notepad >or the DOS version of VEDIT. > >Ted. Thanks Ted, So, I shall not try to use the new Vedit 6.21 Read_Ini(...) and Write_Ini(...) commands to transmit parameters to my Vedit.ini file. At the same time, I think that it is remarkable that I can transmit parameters to Christian's CompDir.vdm file via the new Vedit commands. Thanks to all who made this possible. -peter

Topic: Re: Question about VEDIT.INI Charset parameter (7 of 15), Read 27 times Conf: Installation, Configuration From: Ian Binnie Date: Friday, July 29, 2011 08:13 PM On 7/28/2011 10:01:27 PM, Ted Green wrote: >----- Original Message ----- >> From: "peter rejto" ( rejto@... ) Hi, >> >> After changing the Charset=AMSI or OEM parameter via the {View, Font} >> menu command, the Vedit.ini file does not update this parameter. >> >> Is this peculiar to my installation ? >> >> To be sure, this is not a high priority item for me, since I >> already have a short macro displaying the "actual" Charset parameter. >> >> I just thought no harm done asking. > >The "Typeface=" generally >selects the desired font by >name. The font will then tell >Windows whether it is an OEM >or ANSI font. In the rare case >a font is implemented with two >character sets, the "Charset=" >field will select the desired >one. However, I don't know if >any current font is supplied >that way. >Based on the sizes, weights >and styles available in the >selected font, the "Height=", >"Weight=" and "Italic=" will >select the CLOSEST choice, IF >POSSIBLE. All the common fonts support both ANSI and OEM (at least for Code Page 1252 and Code Page 437) - although even there there are some characters in a couple of fonts with funny glyphs. The OS selects glyphs based on Code Page. NOTE The newer fonts e.g. Consolas don't have a lot of OEM glyphs. There is a Microsoft program (a least for XP) which lets you explore these options. >The issue of fonts and these >parameters in the vedit.ini >file are more complex than I >want to get into. You are >welcome to experiment, but you >would need to read Windows API >programming books to >understand what is really >happening. And even then it is unclear! To use other characters it is necessary to change Code Page - not a trivial task, and requiring a restart. The only way to get extra characters is to go to Unicode. You can even get these in a Console application (but only 256 characters at once) if Unicode is used for display, and changes the Code Page used for translation. I have done this in quite a few programs, using wchar for display, and translating 8 bit characters internally. I actually have written a Characterset Display which shows both ANSI & OEM in a console (by switching Code Page used for translation).

Topic: Re: Question about VEDIT.INI Charset parameter (8 of 15), Read 26 times Conf: Installation, Configuration From: Peter Rejto Date: Friday, July 29, 2011 08:42 PM On 7/29/2011 8:13:44 PM, Ian Binnie wrote: >I have done this in quite a few >programs, using wchar for display, and >translating 8 bit characters internally. >I actually have written a Characterset >Display which shows both ANSI & OEM in a >console (by switching Code Page used for >translation). Hi Ian, Great, I would appreciate a copy of your program. Now, I would like to ask a related question: I have been copying some programs from the Vedit Macro Manual to my Vedit template file. Usually, it is straightforward to translate such a copy into ASCII. I thought that it would be nice to automate this procedure. Do you have any reactions ? Thanks as always, peter

Topic: Re: Question about VEDIT.INI Charset parameter (9 of 15), Read 27 times Conf: Installation, Configuration From: Ian Binnie Date: Sunday, July 31, 2011 08:27 PM On 7/29/2011 8:42:38 PM, peter rejto wrote: >On 7/29/2011 8:13:44 PM, Ian Binnie >wrote: >>I have done this in quite a few >>programs, using wchar for display, and >>translating 8 bit characters internally. >>I actually have written a Characterset >>Display which shows both ANSI & OEM in a >>console (by switching Code Page used for >>translation). > > >Hi Ian, > >Great, I would appreciate a copy of your >program. The following contains a link to the program, and very brief instructions. This also has the source. NOTE You need a suitable font - I suggest Lucida Console http://www.ztw3.com/forum/forum_entry.php?id=108692 >Now, I would like to ask a related >question: > >I have been copying some programs from >the Vedit Macro Manual to my Vedit >template file. Usually, it is >straightforward to translate such a copy >into ASCII. >I thought that it would be nice to >automate this procedure. >Do you have any reactions ? Peter, I am not sure I even understand the question. I haven't done anything like this for years, but don't recollect doing anything other than copy/paste.

Topic: CP437 and CP850 (10 of 15), Read 31 times Conf: Installation, Configuration From: Ian Binnie Date: Sunday, July 31, 2011 08:33 PM Peter, You may be interested in the following, which has an image showing the differences between CP437 and CP850 http://www.ztw3.com/forum/forum_entry.php?id=108673

Topic: Re: Question about VEDIT.INI Charset parameter (11 of 15), Read 27 times Conf: Installation, Configuration From: Peter Rejto Date: Sunday, July 31, 2011 11:05 PM On 7/31/2011 8:27:54 PM, Ian Binnie wrote: > >>Now, I would like to ask a related >>question: >> >>I have been copying some programs from >>the Vedit Macro Manual to my Vedit >>template file. Usually, it is >>straightforward to translate such a copy >>into ASCII. >>I thought that it would be nice to >>automate this procedure. >>Do you have any reactions ? > >Peter, I am not sure I even understand >the question. Thanks Ian, Let me backtrack. I would like to copy an example of a code "snippet" from the Vedit Macro Manual to my Vedit Scratchpad and run it. ( Certainly, with the new {Misc, Execute buffer} menu command, this is easy to do, once the program is in the Vedit Scratchpad. ) I do such a copying from the Macro Manual using the Acrobat Select Utility. I would hope that I end up with an ASCII block. Not quite. I have a hunch that Acrobat uses binary characters to format text. So, I end up with a couple of binary characters that I remove manually. This is the procedure that I would like to automate. To an uninformed person, this translation looks much easier than the ASCCI Unicode translation. This is why I am asking for your reactions. Incidentally, I think that the ability to copy and paste ready made examples of programming tasks is a nice feature of Mathematica and Maple. These are nice mathematics/graphics programs and this is the feature that I would like to import into Vedit. Thanks for everything, -peter

Topic: Re: Question about VEDIT.INI Charset parameter (13 of 15), Read 29 times Conf: Installation, Configuration From: Pauli Lindgren Date: Tuesday, August 02, 2011 07:39 AM On 7/31/2011 11:05:07 PM, peter rejto wrote: > > I do such a copying from the Macro Manual > using the Acrobat Select Utility. > I would hope that I end up with an ASCII > block. Not quite. I have a hunch that > Acrobat uses binary characters to format > text. So, I end up with a couple of > binary characters that I remove > manually. I just tested this. I copied several blocks from the PDF manual to Vedit. I could not see any binary characters in the results, only ASCII. Even if there was a picture in the block that was copied, it was not included, only the ASCII text. I am using Adobe Reader. I don't know if Acrobat works differently. There is a small problem that any indenting in the copied text is lost. (But you can use c-indent.vdm to re-indent it.) This problem does not exist when copying from the Help file. -- Pauli

Topic: Re: Question about VEDIT.INI Charset parameter (12 of 15), Read 28 times Conf: Installation, Configuration From: Pauli Lindgren Date: Tuesday, August 02, 2011 06:03 AM On 7/29/2011 8:13:44 PM, Ian Binnie wrote: > > All the common fonts support both ANSI > and OEM (at least for Code Page 1252 and > Code Page 437) - although even there > there are some characters in a couple of > fonts with funny glyphs. The OS selects > glyphs based on Code Page. No. Only very few fonts support OEM. On my computer, the only ones are "VEDIT Oem" and "Terminal". And I have never seen a font that supports both ANSI and OEM. At least not a fixed pitch font that can be used with Vedit. > > NOTE The newer fonts e.g. Consolas don't > have a lot of OEM glyphs. That is because Consolas does not support OEM. The scripts available in Consolas are Western, Greek, Turkish, Baltic, Central European and Cyrillic. Of course it is possible to re-arrange the glyphs in a font (using a translate table) for example to view DOS (OEM) text files with Windows (ANSI) font. In Vedit, this can be done by setting the ANSI/OEM mode. But this only shows those characters that can be found in the ANSI font. For example the line drawing characters can not be seen. -- Pauli

Topic: Re: Question about VEDIT.INI Charset parameter (14 of 15), Read 26 times Conf: Installation, Configuration From: Ian Binnie Date: Tuesday, August 02, 2011 11:35 PM On 8/2/2011 6:03:20 AM, Pauli Lindgren wrote: >On 7/29/2011 8:13:44 PM, Ian Binnie >wrote: >> >> All the common fonts support both ANSI >> and OEM (at least for Code Page 1252 and >> Code Page 437) - although even there >> there are some characters in a couple of >> fonts with funny glyphs. The OS selects >> glyphs based on Code Page. > >No. Only very few fonts support OEM. >On my computer, the only ones are "VEDIT >Oem" and "Terminal". I should probably have said "All the common fixed pitch fonts". >And I have never seen a font that >supports both ANSI and OEM. I can assure you all these fonts support OEM, although some are missing a few characters - Consolas has no box drawing characters. I have worked extensively with fixed pitch fonts, and my findings are summarised in the following page:- http://ztwiki.com/Selecting+a+custom+font+for+ZTreeWin >At least not >a fixed pitch font that can be used with >Vedit. I see 12 fonts in vedit, but most of these aren't very good. I am pretty sure Lucida Console is enabled by default in XP, although I can't be sure, and it may be necessary to modify the registry as described above. As vedit is a native Windows application, not a Console application, the registry mods shouldn't be necessary. I use Lucida Console extensively, including with vedit. It is true that it is difficult to see the OEM in Lucida Console because vedit doesn't provide any way to select the OEM character set for TrueType fonts, although this can be done by editing vedit.ini (it wouldn't be difficult to change). >> NOTE The newer fonts e.g. Consolas don't >> have a lot of OEM glyphs. > >That is because Consolas does not >support OEM. Microsoft has a free program "Font properties extension setup" (at least for XP) that enhances Character Map and shows all the supported codings. This shows the DOS support for Consolas. >Of course it is possible to re-arrange >the glyphs in a font (using a translate >table) for example to view DOS (OEM) >text files with Windows (ANSI) font. >In Vedit, this can be done by setting >the ANSI/OEM mode. >But this only shows those characters >that can be found in the ANSI font. For >example the line drawing characters can >not be seen. I would not suggest this. Incidentally, it is easy to convert OEM to ANSI by translating OEM to Unicode, then to ANSI. This could probably be done reasonably simply with a macro, and I did something like this, but this does convert some characters and only shows those in the ANSI set. These days I use Unicode for most of my programs, even console programs, and can display characters from both sets.

Topic: Re: Question about VEDIT.INI Charset parameter (15 of 15), Read 23 times Conf: Installation, Configuration From: Ted Green Date: Wednesday, August 03, 2011 05:29 PM At 11:35 PM 8/2/2011, you wrote: >From: Ian Binnie On 8/2/2011 >I should probably have said "All the common fixed pitch fonts". > >>And I have never seen a font that >>supports both ANSI and OEM. > >I can assure you all these fonts support OEM, although some are missing a few characters - Consolas has no box drawing characters. >I have worked extensively with fixed pitch fonts, and my findings are summarised in the following page:- >http://ztwiki.com/Selecting+a+custom+font+for+ZTreeWin ... Thank you for sharing your expertise about fonts. It sure is an incredibly complex topic especially when you get into Unicode fonts/characters. Ted.