newlispfanclub.alh.net

Speaking about good eyes?? That must be a secret hint.. Well, there is nothing too esoteric about it! Japanese has no phonetic equivalent to the L and R consonants but has a consonant that seat somewhere between those 2 sounds. Hence even knowing perfectly well all common place names since childhoo...

m35 wrote:Good eye jp. Read Japanese? Other languages?

Pleased to oblige!
Yes indeed, I read Japanese. And I believe you are a Japanese native speaker since you inadvertently inverted the L for an R in your login summary.

Unfortunately I'm still left with the 梶浦由記 file, and not the proper Unicode one. Perhaps it is worth mentioning that for win2k and above the internal representations are in Unicode UTF-16LE and if one can change arbitrarily its DOS code page, in Windows proper, the internal character repres...

I believe notepad.exe has a UTF-8 option and you could paste those characters into it to have the Chinese chars back. What you would need on Wndows is a cmd.exe which does UTF-8 Lutz Actually for Win2k and above to set the command line to UTF-8 you will have simply to set the code page with the fol...

Lutz Well done everything seems to be fixed except for the best feature of all; the ability of Newlisp to directly communicate with the clipboard. Newlisp-utf8.exe seems to disable completely the clipboard on Unicode and non Unicode based Windows (Win98/ME). Also newlisp-utf8.dll and alas newlisp.dl...

[/quote] Running an equivalent program UTF-8 EXE was able to carry all its calculations and display Japanese without any problems Jean-Pierre ========= Kame.lsp [/quote] Sorry the second statement after (begin (println (car today) " " (cadr today) " " (caddr today)) has to be substituted with …. (pr...

Running Turtle.lsp with the UTF-8 EXE gives an error ' Bad screen distance "302,1612092" '. Running an equivalent program UTF-8 EXE was able to carry all its calculations and display Japanese without any problems Jean-Pierre ========= Kame.lsp ;; Kame.lsp - graphics ;; written by Jean-Pierre Berard...

The localization won’t matter under Win2k or XP since all the internal representations are in Unicode (UTF-16LE). Strictly speaking UTF8 is not Unicode but a coding that lends itself readily to conversion in Unicode(s). The disparity between newlisp-utf8.exe and its UNIX counterpart could come that ...

I don't think you should use the UTF-8 version on Win32 in Germany, where Windows is localized with German as a one-byte-character language, probably with code page ISO-8859. Lutz Indeed under XP with the default code page chcp 437, under the command prompt echo (trim "Höhe;;" ";") > test.txt notep...

Lutz Strangely enough I did try your newlisp-utf8.exe and I found it brakes code when used with UTF8 strings but the regular NewLisp does not Example if you run the strings .. (trim " 日本語が難しい ") ;; Japanish ist schwer (UTF8 i n Japanese) (trim " Er ist ein großer Schwätzer ") ;; Er i...

Thanks Lutz

Now, newlisp_8000rc3_win-tk-111.exe with the change to the font mentioned above runs perfectly under Win98 Japanese.

Jean-Pierre

I did check newlisp_8000rc1_win-tk.exe as well as newlisp-tk.exe v.111 on the following Win98, Win2k, WinXP Pro on the US Edition, they work fine. newlisp v8.0.0 did run well, even under the Win98 Japanese Edition. But newlisp-tk.exe v.107 and the v.111 gave the same following error on the Japanese ...

Thanks Lutz

Perhaps all the outstanding features of the newlisp tk interface should be mentioned in the newlip-tk documentation to ease the interfacing and to prevent the inadvertent 'reinventing of the wheel'.

Jean-Pierre

Easier and little bit faster Jean-Pierre --------------------------- fx.lsp (define (fx) (tk [text] if {[winfo exists .fx] == 1} {destroy .fx} toplevel .fx wm title .fx {File Chooser} frame .fx.fr -borderwidth 10 pack .fx.fr -side top -expand yes -fill y scrollbar .fx.fr.yscroll -orient vertical -co...

Lutz gave a comprehensive entry widget example. Here is listbox widget example. It is a file chooser, where one has simply to click a given file to either open or run it. One can easily extend it to make newlisp to distinguish directories and files and navigate drives and make newlisp to do all sort...

listbox widget example

> It seems that the variable declaration (variable ::display) is not necessary at all.

I guess, it will depend entirely under which context we want the tcl variables to operate on, my impression is from the standpoint of newlisp, (variable display) will always be sufficient.

Jean-Pierre

Actually, 'variable ::varName' declaration and the reference to it with ::varName The advantage of having direct access to tcl variables is to let tk have as many variables as it is deemed necessary for the good conduct of tk widgets processes, but also that newlisp can always modify them at will! J...

Indeed you are right; under a new session newlisp fails to find the variable. Jean-Pierre It works for the title but then I still get "cant read ::display no such variable", I think there was some thing still in your Tcl/Tk namespace from before? Try it with a fresh start of newLISP-tk. Lutz But the...

I realise, if one finds the constant calling of the global variable inopportune, one can directly access the variable with the following... (define (test) (tk "if {[winfo exists .test] == 1} {destroy .test}") (tk "toplevel .test") (tk "variable display") (tk "set display {entry!}") (tk "wm title .te...

Thanks a lot Hans-Peter and Lutz for the prompt replies Actually, I was aware that –textvariable expected a variable name and I did make an attempt to declare display as global but as I could not chain it properly it did fail so I made a synoptic representation instead. Perhaps a paragraph on the ne...

I have been trying to mimic the passing of a tcl variable into the newlisp-tk entry widget but alas, regardless the way I am trying to bring the variable into the entry widget it fails. ============ test.tcl set ok {Entry!} wm title . $ok entry .e -width 30 -textvariable ok pack .e =========== test....