Dear Jerzy - you are absolutely right. It was my fault. Read below about my horrible mistake...
On Mon, 24 Jul 2000 11:47:33 -0400 Jerzy wrote:
>>I was asked to comment on the problems below, reported by Leif.
>>
>>Regarding (a) I agree, you have to make sure that the search is made script insensitive, if that is what you want, because by default it is script sensitive.
Hopefully it is evident from my letter that I spoke about more than this ?! I spoke actually about a request for the next versions of NW and/or NE so that they will present received text in a mix of e.g. cyrillic and english/latin i such a way that both english words and cyrillic words are concidered words. Both when 2xclicking on them and when searching for them with GREP. Currently this is not so, I'm afraid. Not even when you turn *off* script sensitivity. Turning off Script sensitivity and setting the font of this text which I am working with right not resulted in GREP *only* finding words made up of numbers (like 100% etc.)
Let me also in this context mention the socalled "Macro bug when using two-byte languages" which Hakan and Rick just discussed in a likevice labeled subject:
>On Sun, 30 Jul 2000 09:12:01 -0400 Rick Davis wrote:
>>I was under the impression that the macro bug, in which
styled text in a macro creates huge characters in your NW
text window, happened only when using NW 5.1.3 on the Japanese system.
In fact this bug is not only in Japanese system. It is also there when working with cyrillic text. Allthough I have to say that the bug comes and goes - it seems. Sometimes it is there - some times it is not.
>As regards (b) I am afraid that we cannot reproduce what Leif is reporting. So either the problem is confided to a particular setup (system, language kit, extension, hardware, memory conditions etc.. etc., who knows) or we are not doing exactly what you are doing Leif.
>
>To check for the latter possibility, please send me, off-list, a copy of a macro and a file it is supposed to work on, plus the keyboard and system settings , system version number and language kit version (if appropriate) which make it fail.
>
>The font and script of macro command names should not matter at all, as macro commands are also localized into other languages - automatically when the menus are localized. Our Japanese distributors do the localization and the testing in both English and Japanese and have never reported any problems regarding this point.
>
>I am sure that many of you are using Nisus Writer and macros while using non-Roman keyboards, and other than this report, I have not seen any discussion or report of such a problem.
>
>So I suspect that something we do not yet know about is causing the problem to occur.
As mentioned above: the trouble was created by myself. I had had not turned on the FINDER feature regulated by the KEYBOARD control panel that syncronises font and keybord script. Turning that feature on, the macros worked as they should. Which I am very happy indeed to experience !!
You might wonder why I did not notice this ? I might answer that even if that feature are off in Finder and even if neither "Change keyboard to math font scrip" or "Change font to match keyboard script" is turned off in the NW preferences, still changing the keyboard have the effect of changing the font. Allthough not opposite.
I keep also wondering how NW should function if you turn off the keyboard/font syncro within the application itself. Shouldn't one be able then to write in a latin font using cyrillic font ? And why does the keyboard to font syncro work even if I turn everything relating to this both in Keyboard control panel and in NW off ???
Leif Halvard
>>On Sun, 23 Jul 2000 08:16:39 -0400 Leif Silli wrote to NISUS@LISTSERV.DARTMOUTH.EDU
>>>Dear list,
>>
>>>I have from time to time reported that macros, e.g. the reply macro in Email macros vol 1, does not work when a not roman keyboard is selected or when the text is a non-roman. The problem with macros and differents scripts are two things:
>>
>>>a) Things relating to script sensitivity or insensitivity in GREP commands.A well known problem I should say, and relates to the content of the file you are working with.
>>
>>>b) Things relating to the macro verbs themselves. This is little known. I have never seen any report on them and I have just found out myself. The problems relates to the problem when a macro stops when a non-Macroman keyboard i selected in the keyboard menu.
>>
>>>Let us look at the case b) first, since it is one case which I hope Jerzy will comment on. I have found the following to be true: The macro verbs (or "commands") are themselves written in a certain font. That font again belongs a script. Normally they are written in mac roman version of the Any Font or at least in an macroman font. And as soon as I try to run such a macro when the selected keyboard is a non-macroman, something odd will happen. I have a macro that starts by saving the file with a new name. And if the keyboard is cyrillic, the macro simply stops there at the beginning. I also just tried to set the Get adresses font in the Email Macros Vol 1 to a cyrillic Any Font.The macro would run fine as long as the cyrillic keyboard *was* selected. But as soon as I selected a keyboard not in accordance with the script used in the font of the macro verbs/commands the macro forced me to quit NW, which froze the machine.
>>
>>
>>>Jerzy - I hope that you will comment this and make sure this bug/limitation is removed in the next Nisus Writer release. As it is there seem to be no 100% certain method of avoiding the problem. A macro that set the keyboard to a mac roman will not work since the macro would have to have the verbs/commands in a mac cyrillic font, which (I guess) would crash NW *if* the keyboard allready *is* mac roman. BTW, I have not tested if using the Language Register to russify NW will have any impact on the crashing tendence.
>>
>>
>>>If we look at case a) GREP problems arises once you are working with a document in lets say english and cyrillic, where all the text only use a one cyrillic font. This is possible to do since all cyrillic fonts also contain the ASCII (AaZZ) letters. In such a cyrillic font document GREP the Find any word command will only work on the cyrillic text itself. In the english text you will not be able to use that command to find words. Also you won't be able to use the Find any alphabetical character command on anything else than the cyrillic text. If you write in english using a non-macroman font you will also find that that double clicking on a english word will not work.
>>
>>>We are on the way to fixing the problem if we create a wild card character set macro that look for letters in the A-Z range and change the formatting of them to a mac roman font. Then in fact the any word and any alphabetical letter wild card will - when script sensitivity is turned off - find both cyrillic words/alphabetical letters as well as roman alphabetical letters/words. And since also the Any Font is script sensitive you can use that feature to find All text in any cyrillic font or any mac roman font.
>>
>>>Perhaps NW deals with the ASCII letters differently when working with other scripts than the cyrillic ? (I have noted that for the use of Asian Languages there is a setting in the preferences called "Roman text changes font/script with font change".) Is it possible to use the any word wild card on the ascii text in japanese even if the ascii text uses a japanese font ?
>>
>>>Anyway this is a highly interesting topic and one that relates to unicode. The problem arises when mostly when we receive text. And infact it arises everytime we receive non macroman text in our dear new mail client. I think that the proper way to deal with the problem in the current NW versions is to always convert all ASCII text to a mac roman font. Of course the Email Macros should be made to take care of all these aspects
>>
>>>sincerely
>>>Leif Halvard
This archive was generated by hypermail 2b29 : Sat Aug 05 2000 - 23:00:11 AEST