Re: Obsolote entries in "defautl.ui"
On Mon, Jan 27, 2003 at 11:27:26PM +0200, Dekel Tsur wrote: > > I think the first two blocks (break-line, limit) can go as they are > > available elsewhere, and the last (xxalign, ...) should be enabled. > > No, xxalign is an obsolete environment of amsmath. > We should not have it in the menus. Ok. I remember that was the reason they are commented out now. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] cutting math slowness
Hi André, On Tue, 28 Jan 2003, Andre Poenitz wrote: > The attached patch disables the "nice text drawing" and uses plain LaTeX > code instead. I just tried it with xforms and it seems to solve bug 846. Thank you. > Ok to apply? Was it applied? João.
Re: [patch] cutting math slowness
On Wed, Jan 29, 2003 at 12:16:49PM -0200, Joao Luis Meloni Assirati wrote: > > The attached patch disables the "nice text drawing" and uses plain LaTeX > > code instead. > > I just tried it with xforms and it seems to solve bug 846. Thank you. > > > Ok to apply? > > Was it applied? Yes, a few hours ago. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch] cutting math slowness
On Wed, Jan 29, 2003 at 03:29:46PM +0100, Andre' Poenitz wrote: > > I just tried it with xforms and it seems to solve bug 846. Thank you. Btw: Please don't close the bug, but mark it as "feature request". Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
In InitColorLookup [rgb_db.c 85] can't find the rgb color database
Hi there, I'm having a problem with lyx 1.2.3 on gentoo linux. When I try to insert a graphic (.png,.ps,.eps,.xpm) I get: In InitColorLookup [rgb_db.c 85] can't find the rgb color database--No such file or directory In LookupColor [rgb_db.c 177] database uninitialized ... repeated many times When I then scroll down to see the inserted graphic I get: Received unhandled X11 event Type: 0xd Target: 0x3600064 In InitColorLookup [rgb_db.c 85] can't find the rgb color database--No such file or directory In LookupColor [rgb_db.c 177] database uninitialized ... repeated many times and a black box is rendered! If I try to insert a .gif graphic it works as expected. I have used convert to get png from my .ps and then loaded it into gimp and the picture is ok. The .ps and .eps files render in gv and kghostview fine. In lyx they are just rendered as a filled black box, and the error message above is given many times. When I try to "view->postscript" from lyx the images are include ok. I've just rebuilt lyx and still have the problem. Any help in solving this would be appreciated.
Re: In InitColorLookup [rgb_db.c 85] can't find the rgb color database
Chris Bainbridge wrote: > Hi there, I'm having a problem with lyx 1.2.3 on gentoo linux. When I try > to insert a graphic (.png,.ps,.eps,.xpm) I get: > > In InitColorLookup [rgb_db.c 85] can't find the rgb color database--No > such file or directory > In LookupColor [rgb_db.c 177] database uninitialized > ... repeated many times > > When I then scroll down to see the inserted graphic I get: > > Received unhandled X11 event > Type: 0xd Target: 0x3600064 > In InitColorLookup [rgb_db.c 85] can't find the rgb color database--No > such file or directory > In LookupColor [rgb_db.c 177] database uninitialized > ... repeated many times > > and a black box is rendered! > > If I try to insert a .gif graphic it works as expected. I have used > convert to get png from my .ps and then loaded it into gimp and the > picture is ok. The .ps and .eps files render in gv and kghostview fine. In > lyx they are just rendered as a filled black box, and the error message > above is given many times. When I try to "view->postscript" from lyx the > images are include ok. I've just rebuilt lyx and still have the problem. > > Any help in solving this would be appreciated. Hello Chris. This is an error message from the XPM image loader in the xforms library. It is unable to find a file rgb.txt that is part of the standard X11 distribution. Try this at the console to find it: $ find / -name rgb.txt It's a database containing entries like: 255 250 250 snow 25 25 112 MidnightBlue 210 105 30 chocolate 178 34 34 firebrick xforms is braindead in this regard; the possible location of the file is hard-coded as /usr/lib/X11/rgb.txt, /usr/X11R6/lib/X11/rgb.txt, /usr/local/lib/X11/rgb.txt, /usr/openwin/lib/rgb.txt, /XFree86/lib/X11/rgb.txt So, you'll need to create a symbolic link from your file to one of these locations. If the file does not exist (v. unlikely) then your system is probably hosed anyway. If you continue to have problems when converting to xpm format, finding it impossible to display your images, then you've probably come up against a bug in ImageMagick's 'convert' programm that is (probably) doing the grunt work of the conversion process. Run $ lyx -dbg graphics to see exactly what is going on (a script is launched to do the conversion external to LyX). If 'convert' is doing the work and you are still suffering, then I'd suggest defining some converters explicitly (using the Conversion tab of the Preferences dialog). xforms loads ppm files without any known problems, so converters of the form \converter "eps" "ppm" "convert eps:$$i ppm:$$o" "" (stored in you $HOME/.lyx/preferences file) should do the trick. HTH -- Angus
ÐÂÑô¹âÅ®º¢2003Äê1/30-2/ÈÕÌؼ۵¥¼°2002Äê¶ÈÄêµ×»ý·ÖËÍÀñ¹«¸æ
±¾¹«Ë¾´º½ÚÐÝϢʱ¼ä2003Äê2ÔÂ1ÈÕ-2ÔÂ7ÈÕ ±¾ÆÚдº´ÙÏú»î¶¯ÈÕÆÚ£º2003Äê1/30-2/7 ±¾ÆÚÌؼ۵¥Çë¿´¸½¼þ¡£ Èç¹ûÄú²»ÄÜ´ò¿ª¸½¼þ»ò²»Ö§³ÖWORD£¬Çë·¢Óʼþµ½[EMAIL PROTECTED] ÎÒÃÇ»á¸øÄúÖØз¢Ò»·ÝÌؼ۵¥¡£ NewSunGirl 2002ÄêÏ°ëÄê¶È»áÔ±»ý·ÖËÍÀñ»î¶¯¿ªÊ¼ÁË£¡£¡£¡ ÁìÈ¡·½Ê½£º 1£ºÉϺ£¿Í»§¿É×ÔÐÐÈ¥ÑÓ°²Î÷·2299ºÅÊÀóÉ̳Ç4A55ÊÒÁìÈ¡¡£µ«È¥Ö®Ç°±ØÐë´ò021-64014737»ò021-64014738 Óë¿Í·þС½ãºË¶ÔÀۼƻý·Ö·ÖÖµ£¬ÒÔÈ·ÈÏËùÁìÈ¡ÀñÆ·µÄ¼¶±ð¡£ 2£ºÉϺ£ºÍÍâµØ¿Í»§¿ÉÔÚÄúÏ´ζ©»õʱһͬ½«ÀñÆ·Ëͳö¡£ 3£ºÉϺ£ºÍÍâµØ¿Í»§¿É×ÔÐгö10ÔªËÍ»õ·Ñ£¨Óʼķѣ©£¬ÎÒÃǻᾡ¿ì½«ÀñÆ··¢³öË͵½ÄúÊÖÀï¡£ ±¾´Î»ý·ÖÖ»ÊÇ2002Äê6ÔÂ1ÈÕ-12ÔÂ31ÈյĻý·ÖÀÛ»ý¡£ËùÓÐÔÚ2003Äê1Ô¹ºÂòÉÌÆ·µÄ»ý·Ö²»ËãÔÚÄÚ¡£ 2003Äê¶ÈÒѾȡÏûÄêµ×»ý·ÖËÍÀñ»î¶¯£¬¸ÄΪµ±³¡Ïû·Ñµ±³¡ËÍÀñ¡£µ±Àۼƻý·ÖÂú50·Ö¼´¿É»»È¡½ð¿¨£¬½ð¿¨»áÔ±¹ºÂòÉÌÆ·Ò»ÂÉ´ò9ÕÛ£¨½ñÈÕÌؼۺͼ«¸ö±ðÌؼÛÉÌÆ·³ýÍ⣩¡£ Ò»¼¶£º£¨5·Ö£© ½¿À¼Çá±ã¼×ÓͱÊÕýÆ·×°14#Ò»Ö§ + µÂ¹úVENETICÌØЧ·ÀË®´½Ïß±ÊÒ»Ö§£¨´óºìÉ«,ÉîºìÉ«2ÖÖÑÕÉ«Ñ¡Ò»ÖÖ£© + PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÒ»ÖÖ¡£ ¶þ¼¶£º£¨10·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡Ôñ¶þÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + µÂ¹úVENETICÌØЧ·ÀË®´½Ïß±ÊÒ»Ö§£¨´óºìÉ«,ÉîºìÉ«2ÖÖÑÕÉ«Ñ¡Ò»ÖÖ£© Èý¼¶£º£¨15·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄȵ¥·½´¿¾«Ó͹ÒÁ´Ò»¸ù + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÈíĤ·Û£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö塢ƽºâÉ«ËØ£©5¿îÈÎÒâÑ¡Ôñ1°ü + µÂ¹úMISSLY°ë×Ô¶¯´½Ïß±Ê05# dz×Ï¿§·ÈÉ«»ò07# ö¦ºìÉ«ÈÎÑ¡Ò»Ö§ Ëļ¶£º£¨20·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄȵ¥·½´¿¾«Ó͹ÒÁ´Ò»¸ù + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÈíĤ·Û£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö塢ƽºâÉ«ËØ£©5¿îÈÎÒâÑ¡Ôñ1°ü + CLUB"ÎÞÌí¼Ó"κÍÏ´ÃæÔí13¿ËÒ»¿é + CLUB"ÎÞÌí¼Ó"κÍˬ·ôË®30MLһƿ + µÂ¹úMISSLY°ë×Ô¶¯´½Ïß±Ê05# dz×Ï¿§·ÈÉ«»ò07# ö¦ºìÉ«ÈÎÒâÑ¡ÔñÒ»Ö§ Î弶£º£¨25·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄȵ¥·½´¿¾«Ó͹ÒÁ´Ò»¸ù + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÈíĤ·Û£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö塢ƽºâÉ«ËØ£©5¿îÈÎÒâÑ¡Ôñ1°ü + CLUB"ÎÞÌí¼Ó"κÍÏ´ÃæÔí13¿Ë 2¿é + CLUB"ÎÞÌí¼Ó"κÍˬ·ôË®30ML 2Æ¿ + ÈÕ±¾SUKI÷ÈÁ¦ËÄÉ«ÑÛÓ°1ºÐ£¨01#£º¶Å¾éºì¡¢µ¿§·È¡¢ÒøÃ×É«¡¢½ð»ÆÉ«£»03#£ºµ¿§·È¡¢É·È¡¢È⿧·È¡¢·Û¿§·È 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© Áù¼¶£º£¨30·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÈíĤ·Û£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö塢ƽºâÉ«ËØ£©5¿îÈÎÒâÑ¡Ôñ1°ü + ÈÕ±¾CLUB"ÎÞÌí¼Ó"κÍÏ´ÃæÔí13¿Ë 2¿é + ÈÕ±¾CLUB"ÎÞÌí¼Ó"κÍˬ·ôË®30ML 1Æ¿ + ÑÅÊ«À¼÷ì´Å²ÊÓ¨Èó¿Úºì(ÕýÆ·¾«×°£©3.8¿Ë£¨R45# ÑóºìÆ«·ÛÉ« ºÍ06# ÉîºìÆ«´óºìÉ« 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© Æß¼¶£º£¨35·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + ÈÕ±¾CLUB"ÎÞÌí¼Ó"κÍÏ´ÃæÔí13¿Ë 1¿é + ÈÕ±¾CLUB"ÎÞÌí¼Ó"κÍˬ·ôË®30ML 1Æ¿ + ÈÕ±¾CLUB"ÎÞÌí¼Ó"Ã÷íøÐÞ»¤ÑÛ½º 27g + ÈÕ±¾SUKI÷ÈÁ¦ËÄÉ«ÑÛÓ°1ºÐ£¨01#£º¶Å¾éºì¡¢µ¿§·È¡¢ÒøÃ×É«¡¢½ð»ÆÉ«£»03#£ºµ¿§·È¡¢É·È¡¢È⿧·È¡¢·Û¿§·È 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© + ÑÅÊ«À¼÷ì´Å²ÊÓ¨Èó¿Úºì(ÕýÆ·¾«×°£©3.8¿Ë£¨R45# ÑóºìÆ«·ÛÉ« ºÍ06# ÉîºìÆ«´óºìÉ« 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© °Ë¼¶£º£¨40·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + LANCOME Aroma Calm ×Ïŵ»îÁ¦Ïã·Ò15ML һƿ + ÑÅÊ«À¼÷ì´Å²ÊÓ¨Èó¿Úºì(ÕýÆ·¾«×°£©3.8¿Ë£¨R45# ÑóºìÆ«·ÛÉ« ºÍ06# ÉîºìÆ«´óºìÉ« 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© + ÈÕ±¾È«½ø¿Ú¾ø¶ÔƯÁÁµÄPOLA³¬ÈËÆøÌØ»ÝÑÛÓ°£¨Ç³éÏéÂÌ¡¢Ç³·ÈÉ«¡¢Ç³·Ûºì¡¢Ç³½ðÉ«£¬4ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© + CD 2002Äê È«ÐÂÌØЧÈÕÓýô·ôÈéÒº 10ML Ò»¸ö ¾Å¼¶£º£¨45·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÒâÑ¡Ôñ1°ü + ÑÅÊ«À¼÷ì´Å²ÊÓ¨Èó¿Úºì(ÕýÆ·¾«×°£©3.8¿Ë£¨R45# ÑóºìÆ«·ÛÉ« ºÍ06# ÉîºìÆ«´óºìÉ« 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© + ·¨¹úÓÄÀ¼ ORLANE "¼æÃÀ"×ÌÈó˪»ò"Äý¶"Ë®·Ý»¤Àí˪»òÐÞ»¤×ÌÈó˪ 50¿Ë1¸ö Ê®¼¶£º£¨50·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ + Âê¸ñÀöÄÈ·¼Ï㾫ÓÍÃæĤÌû£¨ÃÀ°×È¥Ó¡¡¢½ô·ô±£Êª¡¢°µ´¯·Û´Ì¡¢ÄÛ·ô¿¹Ö壩4¿îÈÎÑ¡1°ü + ÑÅÊ«À¼÷ì´Å²ÊÓ¨Èó¿Úºì(ÕýÆ·¾«×°£©3.8¿Ë£¨R45# ÑóºìÆ«·ÛÉ« ºÍ06# ÉîºìÆ«´óºìÉ« 2ÖÖÑÕÉ«ÈÎÑ¡Ò»ÖÖ£© + ·¨¹úÓÄÀ¼ ORLANE "¼æÃÀ"×ÌÈó˪»ò"Äý¶"Ë®·Ý»¤Àí˪»òÐÞ»¤×ÌÈó˪ 50¿Ë1¸ö + CD 2002Äê È«ÐÂÌØЧÈÕÓýô·ôÈéÒº 10ML Ò»¸ö ʮһ¼¶£º£¨55·Ö£© PelicanÈÕ±¾"Ó£Ö®»¨"´¿Ö²Îﾵ䷼Ï㾫ÓÍ£¨Ììóÿû¡¢Ïã³È¡¢ÆÏÌÑèÖ£©ÈÎÒâÑ¡ÔñÈýÖÖ+¾«ÃÀÅäÌ×Ïã޹¯ºÍÎÞÑÌÀ¯ÖòÒ»ºÐ10¸ö + Âê¸ñÀöÄÈ·¼Ï
Re: CJK-LyX-1.2.3
On Tue, 28 Jan 2003, Angus Leeming wrote: > Of course, I don't know what I'm doing when it comes to the nitty gritty of > creating an input context, I don't know about the input context any more than you don't, but somebody has to deal with it to solve the CJK-LyX problem,sigh... >but can't you create and then destroy a new one > each time you toggle the input method? That's what my patch to input.c > does. Well, my test shows that your input.c still does not change the input context, i.e., preedit position, etc. The code looks fine to me but it does not function as expected. > The code compiles and DOES NOT CRASH when I use it, so that's a start. In your "trial" xforms box, I can link with the input method. That is I can compose CJK-characters through input method, but when I hit "space-bar" on the keyboard, the composed CJK-characters disappear from the box. > assume that you'll have to move the code in lyxim into the xforms library > to actually proceed from here (input CJK) but that was the point of the > excercise wasn't it? Yes, that was my intention. Oh, by the way, the "DUMMY_FONT_NAME" is #define DUMMY_FONT_NAME "-*-*-*-r-normal--14-130-75-75-*-*" Regards, cghan
Re: In InitColorLookup [rgb_db.c 85] can't find the rgb color database
Angus, thanks for your help. This seems to have been a bug in xforms 1.0_rc4 used in gentoo. I just installed 1.0 final and its working (still get the unhandled x11 event though).
Re: CJK-LyX-1.2.3
On Wednesday 29 January 2003 4:42 pm, [EMAIL PROTECTED] wrote:
> On Tue, 28 Jan 2003, Angus Leeming wrote:
> > Of course, I don't know what I'm doing when it comes to the nitty gritty
> > of creating an input context,
> I don't know about the input context any more than you don't, but somebody
> has to deal with it to solve the CJK-LyX problem,sigh...
> >but can't you create and then destroy a new one
> > each time you toggle the input method? That's what my patch to input.c
> > does.
> Well, my test shows that your input.c still does not change the input
> context, i.e., preedit position, etc. The code looks fine to me but it
> does not function as expected.
This is with my note about setting location.x = ob->x etc?
Perhaps you have to
if (flcontext->xic)
XDestroyIC(flcontext->xic);
before you create a new one.
Also, a quick 'grep xic' of the xforms sources comes up with
case FocusIn:
if (fl_context->xic)
{
M_info("Focus", "Setting focus window for IC");
XSetICValues(fl_context->xic,
XNFocusWindow, st_xev.xfocus.window,
XNClientWindow, st_xev.xfocus.window,
0);
}
break;
If you re-create the IC, then presumably you have to do this too?
> > The code compiles and DOES NOT CRASH when I use it, so that's a start.
> In your "trial" xforms box, I can link with the input method. That is I
> can compose CJK-characters through input method, but when I hit
> "space-bar" on the keyboard, the composed CJK-characters disappear from
> the box.
I'm getting confused. This is using an unmodified xforms1.0 or using the
changes you've made already to fl_initialize? Presumably it's not with my
suggested change to input.c because that doesn't create a IC at all?
Anyway, for the present problem, it doesn't really matter whether you create
an IC just once, in flinitialize, or if you do it dynamically in input.c.
You tell me that you have created a pre-edit area and can use it successfully.
Your problem lies in the final step when returning to 'nornal' mode? But, my
question to you is: how does the code know what 'normal' mode is? At present
'space' means nothing special to the xforms code. Are you not still in
preedit mode and have just typed a space in your preedit area?
Why not test this hypothesis with a little
if (key == XK_Space)
return 0;
in input.c (since you're not yet manipulating the IC using Shift-Space and
Space) before any change to the widget is made.
> > assume that you'll have to move the code in lyxim into the xforms
> > library to actually proceed from here (input CJK) but that was the
> > point of the excercise wasn't it?
> Yes, that was my intention.
Being generally ignorant of all this, I'm actually amazed that you can get
anything at all before merging this code into the library. What will the code
in lyxim give you once you have resolved your problems with the IC?
> Oh, by the way, the "DUMMY_FONT_NAME" is
> #define DUMMY_FONT_NAME "-*-*-*-r-normal--14-130-75-75-*-*"
Ok.
Am I correct in saying that I can't actually test things at all from this end
because the input method is actaully a daemon process running in the
background. I have vague memories of helping a Japanese visitor to the lab
set up his machine so that he could use emacs in this way.
I also seem to remember that he used it as a two step process. in step 1 he
created a symbol from a number of key presses and then in step 2 he used
arrow keys to toggle between several possible kanji characters. Is this
second part the external input method?
It seems to me that you should post a question to some eastern mailing list
where you're more likely to find experts at this sort of thing.
Sorry I can't be of more help.
Best wishes,
Angus
Re: CJK-LyX-1.2.3
On Wed, 29 Jan 2003, Angus Leeming wrote:
> It seems to me that you should post a question to some eastern mailing
list
> where you're more likely to find experts at this sort of thing.
>
> Sorry I can't be of more help.
> Best wishes,
> Angus
I can feel your frustration, but here's a question I'm sure you can
answer:
The usual way of changing the input context is using "XSetICValues".
For example, if you have create ic in lib/flresource.c as
[I]
XPoint location;
location.x = 0;
location.y = 0;
XVaNestedList preedit_list;
preedit_list = XVaCreateNestedList( 0,
XNSpotLocation, &location,
XNFontSet, fontset,
NULL);
fl_context->xic = XCreateIC(fl_context->xim,
XNInputStyle, xim_style,
XNPreeditAttributes, preedit_list,
XNStatusAttributes,status_list,
0);
XFree(preedit_list);
then, the preedit-composition starts at (x=0,y=0). Now, Changing the
above in flresource.c into
[II]*
XPoint location;
location.x = 0;
location.y = 0;
XVaNestedList preedit_list;
preedit_list = XVaCreateNestedList( 0,
XNSpotLocation, &location,
XNFontSet, fontset,
NULL);
fl_context->xic = XCreateIC(fl_context->xim,
XNInputStyle, xim_style,
XNPreeditAttributes, preedit_list,
XNStatusAttributes,status_list,
0);
XFree(preedit_list);
location.x = 20;
location.y = 0;
preedit_list = XVaCreateNestedList( 0,
XNSpotLocation, &location,
NULL);
XSetICValues(fl_context->xic,XNPreeditAttributes,preedit_list,0);
XFree(preedit_list);
makes the preedit-composition starts at (x=20,y=0) instead of (x=0,y=0).
Now if I maintain code [I] in flresource.c and put
*
location.x = 20;
location.y = 0;
preedit_list = XVaCreateNestedList( 0,
XNSpotLocation, &location,
NULL);
XSetICValues(fl_context->xic,XNPreeditAttributes,preedit_list,0);
XFree(preedit_list);
**
into turn_on_local_input in input.c such as
***
static void turn_on_local_input(FL_OBJECT * ob)
{
SPEC *sp = ob->spec;
printf("Turning on CJK local input\n");
sp->CJK_local_input = 1;
if (fl_context->xic)
XDestroyIC(fl_context->xic);
XPoint location;
location.x = 20;
location.y = 0;
XVaNestedList preedit_list;
XVaNestedList status_list;
preedit_list = XVaCreateNestedList( 0,
XNSpotLocation, &location,
// XNFontSet, fontset,
NULL);
XSetICValues(0,XNPreeditAttributes,preedit_list,0);
XFree(preedit_list);
}
*
I should expect the same effect, right? Wrong! No change of xic. That is,
with this input.c, the composition starts at (x=0,y=0) instead of
(x=20,y=0). What goes wrong here? I'm sure you get me right this time.
Regards,
cghan
Re: CJK-LyX-1.2.3
[EMAIL PROTECTED] wrote:
> Now if I maintain code [I] in flresource.c and put
>
>
> *
> location.x = 20;
> location.y = 0;
> preedit_list = XVaCreateNestedList( 0,
> XNSpotLocation, &location,
> NULL);
> XSetICValues(fl_context->xic,XNPreeditAttributes,preedit_list,0);
> XFree(preedit_list);
> **
>
> into turn_on_local_input in input.c such as
>
> ***
> static void turn_on_local_input(FL_OBJECT * ob)
> {
> SPEC *sp = ob->spec;
>
> printf("Turning on CJK local input\n");
> sp->CJK_local_input = 1;
> if (fl_context->xic)
> XDestroyIC(fl_context->xic);
>
> XPoint location;
> location.x = 20;
> location.y = 0;
> XVaNestedList preedit_list;
> XVaNestedList status_list;
>
> preedit_list = XVaCreateNestedList( 0,
>XNSpotLocation, &location,
> // XNFontSet, fontset,
> NULL);
> XSetICValues(0,XNPreeditAttributes,preedit_list,0);
>
> XFree(preedit_list);
> }
> *
>
> I should expect the same effect, right? Wrong! No change of xic. That is,
> with this input.c, the composition starts at (x=0,y=0) instead of
> (x=20,y=0). What goes wrong here? I'm sure you get me right this time.
Dear CG, thanks for the explanation. I now understand that we need only one
IC (per dialog?) and that we can change it's position using XSetICValues.
Great, I've learnt something new.
However, and without meaning to be rude, your code in input.c is barmy ;-)
1. No IC exists anymore:
if (fl_context->xic)
XDestroyIC(fl_context->xic);
2. You are setting the value of a null IC
XSetICValues(0,XNPreeditAttributes,preedit_list,0);
What happens if you remove the lines of 1 and modify two to
XSetICValues(fl_context->xic,XNPreeditAttributes,preedit_list,0);
as it is in your example II.
--
Angus
Re: lyx-devel po/: ChangeLog postats.sh
Hi Angus, Rewrite postats.sh to: 1. Not need the existence of a Makefile in order to run; 2. Not result in php warnings about uninitialised variables if any of the translated, fuzzy or untranslated strings are missing. Why did have to rewrite the script completely for the two reasons above??? We could have replaced the makefile invocation by a one-line patch. And there are already checks for uninitialized variables in the code. If I missed a place, a local change of a few lines would have been sufficient. The new code is _much_ longer. I prefer short and simple solutions as they can be maintained more easily. IMHO functions like "dump_tail" only introduce overhead. Michael
Re: lyx-devel po/: ChangeLog postats.sh
Michael Schmitt <[EMAIL PROTECTED]> writes: | The new code is _much_ longer. I prefer short and simple solutions as | they can be maintained more easily. IMHO functions like "dump_tail" | only introduce overhead. I am not sure that I agree... -- Lgb
Re: lyx-devel po/: ChangeLog postats.sh
On Wednesday 29 January 2003 6:47 pm, Michael Schmitt wrote:
> Hi Angus,
>
> > Rewrite postats.sh to:
> > 1. Not need the existence of a Makefile in order to run;
> > 2. Not result in php warnings about uninitialised variables if any of the
> > translated, fuzzy or untranslated strings are missing.
>
> Why did have to rewrite the script completely for the two reasons
> above??? We could have replaced the makefile invocation by a one-line
> patch. And there are already checks for uninitialized variables in the
> code. If I missed a place, a local change of a few lines would have been
> sufficient.
>
> The new code is _much_ longer. I prefer short and simple solutions as
> they can be maintained more easily. IMHO functions like "dump_tail" only
> introduce overhead.
Oh, come on; dumphead and dumptail are an irrelevance to the process of
extracting the info. Much better to shove them out of the way.
Let's move on to the actual process of extracting info from the msgfmt run. It
is more interesting and was quite challenging. You put a lot of effort into
it and I didn't mean to stand on your toes. If you feel hurt, I apologise
profusely.
That said, perhaps if I explain why I made my changes, my motivation will be
clearer.
If you've got the code that I submitted this afternoon, then you'll see that
the main code is all in one single function that fills a single variable
$output. Given that run_msgfmt fills $output, what is confusing about this
code?
while [ $# -ne 0 ]
do
run_msgfmt $1
shift
if [ $# -eq 0 ]; then
echo "${output});"
echo '?>'
else
echo "${output},"
echo
fi
done
It also has the pretty-printing advantage that the ',' now appears on the same
line as the array element.
Moving into run_msgfmt itself and the extraction of strings from the output of
msgfmt.
Point 1. The .* RE operator is EXTREMELY greedy. Try and avoid it if at all
possible.
Point 2. Sometimes 'cut' is a better tool than 'sed'. I repectfully submit
that this:
input=`grep "Last-Translator" $pofile` && {
# Remove 'Last-Translator: ' from the front of the string
input=`echo $input | sed 's/ */ /g' | cut -d ' ' -f 2-`
# The string now consists of "Jo Bloggs ..."
# Use the < and > to extract the two parts.
translator=`echo $input | cut -d '<' -f 1 | sed 's/ *$//'`
email=`echo $input | cut -d '<' -f 2 | cut -d '>' -f 1`
}
is cheaper and more robust than this:
grep "Last-Translator" $x |
sed -e 's/"Last-Translator: \(.*\)\( *\)<\(.*\)>\\n"/"translator" =>
"\1",
"email" => "\3", /'
(Because .* is extremely greedy and multiple instance /can/ do weird things.
I'm not saying that they did here, but you get my point.)
Point 3. This is very neat and compact:
make 2>&1 $y.gmo | grep "^[1-9]" |
sed -e 's/\([0-9]*\) translated m[a-z]*[.,]/"msg_tr" => \1,/' |
sed -e 's/\([0-9]*\) fuzzy t[a-z]*[.,]/"msg_fu" => \1,/' |
sed -e 's/\([0-9]*\) untranslated m[a-z]*./"msg_nt" => \1,/'
But it fails totally if there are no untranslated or fuzzy strings. (msgfmt
simply doesn't output anything about them.)
Remember, last night I generated a php3 page and found it chock full of
warnings. I had no idea why, so had to go hunting. I tried to modify the code
above and failed. In fact, I think it's impossible to get right like this
because it presupposes the existence of a string "xxx fuzzy messages".
That said, it is quite simple to have an integer variable initialised to zero
and to fill it with xxx if the string exists. That's all I did. Granted, I
used a single function for all three extractions because I, personally,
prefer functions ;-)
# $1 is a string like
# '588 translated messages, 1248 fuzzy translations, 2 untranslated messages.'
# Any one of these substrings may not appear if the associated number is 0.
#
# $2 is the word following the number to be extracted,
# ie, 'translated', 'fuzzy', or 'untranslated'.
#
# extract_number fills var $number with this number, or sets it to zero if the
# word is not found in the string.
extract_number () {
test $# -eq 2 || error 'extract_number expects 2 args'
number=0
echo $1 | grep $2 >/dev/null || return
# It /is/ safe to use 'Z' as a delimiter here.
number=`echo $1 | sed "s/\([0-9]*\)[ ]*$2/Z\1Z/" | cut -d 'Z' -f 2`
}
Best regards,
Angus
ps I'm willing to admit that 'unset' is a little excessive ;-)
A
St Maarten, the caribbean
Ever thought of owning a piece of paradise?? Want to live on a warm year round international flavor island? Looking for investment property in the Caribbean? Different real estate has now available a limited number of prestigous properties available for sale on the duty free island of St Maarten-St Martin. Check out http://www.differentrealestate.com Or e-mail [EMAIL PROTECTED] Ever thought of owning a piece of paradise.txt Description: Binary data
Re: CJK-LyX-1.2.3
Hello, Angus; On Wed, 29 Jan 2003, Angus Leeming wrote: > Dear CG, thanks for the explanation. I now understand that we need only one > IC (per dialog?) and that we can change it's position using XSetICValues. > Great, I've learnt something new. I am glad that I can still hold your interest here. > 1. No IC exists anymore: > if (fl_context->xic) > XDestroyIC(fl_context->xic); Yes, it is barmy! > 2. You are setting the value of a null IC > XSetICValues(0,XNPreeditAttributes,preedit_list,0); > Oops, my mistake! > What happens if you remove the lines of 1 and modify two to > XSetICValues(fl_context->xic,XNPreeditAttributes,preedit_list,0); > as it is in your example II. Still the same. The precomposition point does not move... cghan
Re: [patch] scroll line by line when mouseing
John Levon <[EMAIL PROTECTED]> writes: | It still has exactly the same regressions I pointed out to you with the | previous patch. Try TableExamples.lyx, the cursor gets stuck in tables | and it is impossible to scroll-select through the whole of | TableExamples.lyx. I'll look a bit more on this. (please beat me too it...) | The question is whether this is a net improvement or not. So I need some response whether this patch should go in or not. My feeling is that it should go in, but it is a bit large. And might make some things worse... Even if I cannot understand why... -- Lgb
Feature request
Hi all, Just a (very) minor annoyance with the QT frontend in 130cvs. From memory 1.2.x allowed you to insert a cross reference without closing the cross reference window. Under 130cvs, inserting the reference closes the window, which is a tad annoying if you want to insert something like blah blah equations (1) to (6) blech, Maybe an apply button would be useful? Rod _ rod | "Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea." | They Might Be Giants, Lincoln
Re: Feature request
On Thu, Jan 30, 2003 at 10:42:10AM +0800, Rod Pinna wrote: > Just a (very) minor annoyance with the QT frontend in 130cvs. From memory > 1.2.x allowed you to insert a cross reference without closing the cross > reference window. Under 130cvs, inserting the reference closes the window, > which is a tad annoying if you want to insert something like > > blah blah equations (1) to (6) blech, > > Maybe an apply button would be useful? This seems to be an oversight. Please file a bug at https://bugzilla.lyx.org regards john
Re: CJK-LyX-1.2.3
Sorry, I don't have time to look at the source (Bright now. (BSo here are only vague general remarks. (B (BXIM is designed to be created only once for an X (Bconnection. Don't create more than one XIM (Bnor destroy and recreate again and again. (BXlib can be quite fragile, (especially you tried (Bto create multiple XIM in different locales.) (B (BShift+Space doesn't connect/create nor disconnect/ (Bdestroy XIM. XIM servers are programmed to toggle (Bconversion service. They are kept connected. (B (BMulti_Key diacritics composition is an XIM server (Bbuilt into Xserver. Other XIM server must be (Brunning external to Xserver process. (B (BXIC is designed to be created for each GC (graphic (Bcontext). Especially, each window (widget) must (Bhave its own input context if it expects user input. (BThe current design of xforms is flawed that it (Bcreates only process global XIC and tries to use it (Bfor all widgets. Just consider the disaster it (Bcauses if a user changes focus across windows sharing (Bthe same input context during a conversion. (B (BHope some of the remarks above can be of a help. (B (BRegards, (BSMiyata
Re: CJK-LyX-1.2.3
Hello, Miyata: Glad to hear from you. On Thu, 30 Jan 2003, Shigeru Miyata wrote: > Sorry, I don't have time to look at the source > right now. > So here are only vague general remarks. > > XIM is designed to be created only once for an X > connection. Don't create more than one XIM > nor destroy and recreate again and again. > Xlib can be quite fragile, (especially you tried > to create multiple XIM in different locales.) I see. That means one of two xims, which are in lyxim.C of CJK-LyX and in flresource.c of xforms, should be removed. Correct? This also means that for CJK-LyX, all the stuffs in lyxim.C should be imported into xforms library. Right again? > XIC is designed to be created for each GC (graphic > context). Especially, each window (widget) must > have its own input context if it expects user input. > The current design of xforms is flawed that it > creates only process global XIC and tries to use it > for all widgets. Sorry for my ignorance. Can you be more specific or detailed ? > Hope some of the remarks above can be of a help. You surely are helping me! Regards, cghan
Re: [Bug 848] IEEEtran reference should be updated
On Tue, 28 Jan 2003 [EMAIL PROTECTED] wrote:
> http://bugzilla.lyx.org/show_bug.cgi?id=848
I get "Error 400" attempting to get to bugzilla.lyx.org
> [EMAIL PROTECTED] changed:
>
>What|Removed |Added
>
> CC||[EMAIL PROTECTED]
> Status|UNCONFIRMED |NEW
> everconfirmed|0 |1
>
>
>
> --- Additional Comments From [EMAIL PROTECTED] 2003-01-28 11:16 ---
> It appears that we do not have any documentation for IEEEtran in
> Extended.lyx, but rather some documentation for latex8.
So far so good.
> Allan, am I right that latex8 should be dead now?
No. I don't think so. Latex8 is/was for conference papers. The very
latest IEEEtran has a "conference" option but I'm not sure if all
conferences are using that.
> Can we just use IEEEtran instead? Also I see that authors and
> affiliations handling require special code that lyx cannot do now,
> like \author(\authorblockN{John Doe}\authorblockA{address\on
> several\\lines}}
I did a quick test with one of my old docs yesterday and found that it
still formatted the same as before so I don't think it is too much to
worry about yet. Although it would be nice to figure out how to
support it.
> Finally, IEEEtran has two modes, namely conference and journal (journal is
> default). Should we provide a different layout for conferences?
I've only have a quick glimpse of the latest code and haven't tested
any of the options yet. Plenty of conference papers get turned into
journal papers so it would be simpler if they were the same class --
mind you if IEEEtran(conference) consisted of just:
input IEEEtran_journal
extra_option conference
without any environment name changes (although font etc. info might
change) then it wouldn't hurt but would also be overkill methinks.
Allan. (ARRae) (not subscribed yet but will be soon)
[PATCH] InsetInclude and version control bug
An annoying bug in multipart document support occurs when you use a VCS like RCS on the documents. Load the master, update DVI to get all the other parts loaded, now try to edit one of the auto-loaded docs. You can't because the lyxvc for that document wasn't setup. A simple one line fix is attached. I considered moving the lyxvc code from loadLyXFile() into readFile() instead but decided that would be too dramatic and probably not the right thing to do anyway. Besides, I want this change in 1.3.0 if it isn't already out the door. I keep getting "Error 400" when trying to access bugzilla.lyx.org. Any ideas? Allan. (ARRae) Index: src/insets/ChangeLog === RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/ChangeLog,v retrieving revision 1.552 diff -u -p -r1.552 ChangeLog --- src/insets/ChangeLog23 Jan 2003 16:23:41 - 1.552 +++ src/insets/ChangeLog30 Jan 2003 04:05:54 - @@ -1,3 +1,8 @@ +2003-01-27 Allan Rae <[EMAIL PROTECTED]> + + * insetinclude.C (loadIfNeeded): included files might be under + VCS control so we need loadLyXFile() not readFile() for that. + 2003-01-20 Michael Schmitt <[EMAIL PROTECTED]> * insetert.C: Index: src/insets/insetinclude.C === RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/insetinclude.C,v retrieving revision 1.91 diff -u -p -r1.91 insetinclude.C --- src/insets/insetinclude.C 4 Dec 2002 12:07:48 - 1.91 +++ src/insets/insetinclude.C 30 Jan 2003 04:05:54 - @@ -274,7 +274,7 @@ bool InsetInclude::loadIfNeeded() const if (!finfo.isOK()) return false; - return bufferlist.readFile(getFileName(), !finfo.writable()) != 0; + return bufferlist.loadLyXFile(getFileName(), false) != 0; }
Re: [PATCH] InsetInclude and version control bug
> > I keep getting "Error 400" when trying to access bugzilla.lyx.org. > Any ideas? You get that with http://... (at least I do). Try it with https://... Rod _ rod | "Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea." | They Might Be Giants, Lincoln
Re: [PATCH] InsetInclude and version control bug
On Thu, 30 Jan 2003, Rod Pinna wrote: > > I keep getting "Error 400" when trying to access bugzilla.lyx.org. > > Any ideas? > > You get that with http://... (at least I do). Try it with https://... Thanks Rod. It seems out bugzilla mailer inserts the wrong protocol for the website. Allan. (ARRae)
Re: lyx-devel po/: ChangeLog postats.sh
On Wed, Jan 29, 2003 at 07:41:31PM +, Angus Leeming wrote:
> Point 1. The .* RE operator is EXTREMELY greedy. Try and avoid it if at all
> possible.
Indeed.
> Point 2. Sometimes 'cut' is a better tool than 'sed'. I repectfully submit
> that this:
>
> input=`grep "Last-Translator" $pofile` && {
> # Remove 'Last-Translator: ' from the front of the string
> input=`echo $input | sed 's/ */ /g' | cut -d ' ' -f 2-`
> # The string now consists of "Jo Bloggs ..."
> # Use the < and > to extract the two parts.
> translator=`echo $input | cut -d '<' -f 1 | sed 's/ *$//'`
> email=`echo $input | cut -d '<' -f 2 | cut -d '>' -f 1`
> }
>
> is cheaper and more robust than this:
> grep "Last-Translator" $x |
> sed -e 's/"Last-Translator: \(.*\)\( *\)<\(.*\)>\\n"/"translator" =>
>"\1",
Concerning cheapness:
y=${x%<*}
translator=${j#* }
y=${x#*<}
email=${y%>*}
should beat that. But that's a bash-ism, isn't it?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
