Thank you for taking the time to write such detailed responses! I will see what I can do with your suggestions. Fred On Jan 31, 2005, at 3:49 PM, Peter Dyballa wrote: <snip> Frederick M. Hoyt www.livejournal.com/users/frederickhoyt
On Feb 1, 2005, at 4:38 AM, Peter Dyballa wrote: > The fontset you have to supply is already on > http://www.m17n.org/emacs-bidi/ described. I had put in my .emacs file > before starting a new Emacs. Choosing than the new 'default' fontset > let me see the Arabic text. > > ftp://ftp.m17n.org/pub/mule/.notready/emacs-bidi-0.9.1.tar.gz > obviously is source code. You'll need to configure and compile, for > which you'll need Apple's Developer Tools ... I have tried this several times, and while the .configure script succeeds, make chokes. There is a long list of error messages which seem to fall into four general categories: macgui.h:26: error: conflicting types for `X' /usr/X11R6/include/X11/X.h:107: error: previous declaration of `X' (for some X) /usr/X11R6/include/X11/Xlib.X: error: previous declaration of `Y' (for some X and Y) macgui.h:X: error: redefinition of `Y' (for some X and Y) /usr/X11R6/include/X11/X.P: error: `Q' previously declared here (for some P and Q) These errors occur regardless of whether I fun make from an Xterm or the OS X terminal. I thought there might be a conflict with(Continue reading)
Am 01.02.2005 um 15:49 schrieb Frederick Hoyt:
> On Feb 1, 2005, at 4:38 AM, Peter Dyballa wrote:
>
>> ftp://ftp.m17n.org/pub/mule/.notready/emacs-bidi-0.9.1.tar.gz
>> obviously is source code. You'll need to configure and compile, for
>> which you'll need Apple's Developer Tools ...
>
> I have tried this several times, and while the .configure script
> succeeds, make chokes. There is a long list of error messages which
> seem to fall into four general categories:
It depends on the options to configure to when making of this bidi
Emacs fails. The best results I've seen come with
./configure --with-carbon --without-x
Compilation ends with
gcc -Demacs -DHAVE_CONFIG_H -I. -I/Users/pete/Quellen/emacs-bidi/src
-fpascal-strings -fno-common -DMAC_OSX -I../mac/src -Dtemacs
-I/sw/include -L/sw/lib
/Users/pete/Quellen/emacs-bidi/src/prefix-args.c -o prefix-argsgcc
-prebind -framework Carbon -lstdc++ -Xlinker -headerpad -Xlinker 690
-L/sw/lib -o temacs pre-crt0.o dispnew.o frame.o scroll.o
xdisp.o xmenu.o window.o charset.o coding.o category.o ccl.o
bidi.o cm.o term.o xfaces.o emacs.o keyboard.o macros.o
keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o
fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o
(Continue reading)
On Feb 1, 2005, at 10:05 AM, Peter Dyballa wrote: > Why do you need GNU Emacs for Arabic or Hebrew? Partly because I'm just curious and like to tinker, but mostly because I prefer using emacs for latex, and use xelatex for Arabic. Texshop allows Arabic text entry (albeit from left-to-right), but for a variety of reasons texshop isn't my first choice for editing. My assumption is that if I could get Arabic working in emacs, I should be able to use it for typesetting arabic in xelatex. Of course, I could in principle just enter the unicode values for the arabic, but that's doesn't seem like a viable option. However, I will also try to follow your instructions for defining fontsets for Carbon Emacs, as opposed to emacs under X11. I also am interested in being able to use the Arabic script in other projects, such as writing regular expressions in Perl, or for grammar development in NLP environments which only run under X11. Otherwise, I do have several means for Arabic text editing in Aqua: TextEdit, Mellel, Texshop, and good old Nisus Writer under Classic. Thanks as always, Fred ________________________________(Continue reading)
On Feb 1, 2005, at 10:05 AM, Peter Dyballa wrote: > It depends on the options to configure to when making of this bidi > Emacs fails. The best results I've seen come with > > ./configure --with-carbon --without-x > <snip> > This was completely without X11 (although I think it is not really > prepared to be compiled as a Carbon application). With X11 the > compilation finishes quicker, with different errors for me. I think > the code is two or three years to old to get compiled. It might work > with Mac OS X less than 10.2.8, or after installing this and an even > elder SDK from the Mac OS X 10.3 DVD and making this SDK the default > for compilation (which I never tried). Then the recent X11R6.6 can be > to modern and you would have to go back X11R6.5 or X11R6.4. > Ok, I have tried this only with the 10.3 SDK installed. I will install the older versions and see what happens. Fred ________________________________ "Hell is other people at breakfast." - Sartre(Continue reading)
Am 31.01.2005 um 22:49 schrieb Peter Dyballa: > The Mac OS X install CD or DVD has fonts for other scripts (Arabic and > Hebrew): > > AlBayan.ttf, AlBayanBold.ttf, ArialHB.ttf, ArialHBBold.ttf, > Baghdad.ttf, DecoTypeNaskh.ttf, NewPeninimMT.ttf, > NewPeninimMTBold.ttf, NewPeninimMTBoldInclined.ttf, > NewPeninimMTInclined.ttf, Raanana.ttf, RaananaBold.ttf. > I checked these fonts in Unicode Font Info (I tried the same with ttf1afm) and it seems that all these Arabic and Hebrew fonts have their proper glyphs at the correct Unicode positions (mule-unicode-0100-24ff) and have in their Private Use Areas (mule-unicode-e000-ffff) the Alphabetic Presentation Forms. So they are structurally identical to the BDF and PCF versions as supplied with the source code (which contain other scripts too!). Under X11 you can view the fonts with X Font Display: xfd -fn '-(Continue reading)m17n-*--20-*-iso10646-1' Please notice the single quotes to escape the asterisks in the font selection expression. (And it seems I have learned a bit more about creating Unicode compatible fontsets that might work in the Carbon Emacsen too!) --
Hi all, i'm using the flyspell-mode with the dp CarbonEmacs to check the spelling of my buffers on the fly. I installed aspell also via darwinports. As suggested in the aspell's users's guide i put the following line in my site-start.el: (setq-default ispell-program-name "aspell") i also have the following lines there: (flyspell-mode 1) (diminish 'flyspell-mode) (setq ispell-parser 'tex) Everything was working fine when i edited my last document in english but now i have something i german but if i want to change the dictionary using the tools->speel checking menu i only get the following message: Starting new Ispell process... ispell-init-process: Unhandled Error: Expected language "en" but got "de". If i open a LaTeX document i get the following messages in the *Message* buffer: Loading flyspell...done (Next local Ispell command will use deutsch8 dictionary) [2 times] Starting new Ispell process... File mode specification error: (error "Unhandled Error: Expected language \"en\" but got \"de\".")(Continue reading)
Hi all, i just noticed another weird thing. Using AUCTeX's newest release 11.55 the mode line will show 'Fundamental' instead of 'LaTeX' when opening a .tex file. AuCTeX is loaded, i.e. the menus are there C-c C-c is working and the minor-modes are loaded which i added in the LaTeX-mode-hook. As before, i can't remember any other change in my system. Is anyone using the latest AUCTeX and can confirm my findings? Thanks Martin -- -- Sex without love is an empty experience, but, as empty experiences go, it's one of the best. -- Woody Allen
Am 10.02.2005 um 14:56 schrieb Martin Buchmann:
> Is anyone using the latest AUCTeX and can confirm my findings?
Just tried it, and ran into the same situation: no bib-cite.el. Reason:
we did not
sudo make -k install-contrib
I wonder why it worked with AUCTeX 11.53! The Makefiles are almost the
same.
I'll have to update my description on how to install AUCTeX too,
tomorrow. Actually it's already today!
--
Mit friedvollen Grüßen
Pete
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
Pete, thanks for the hint. I installed the contrib files too. I just learned that (setq debug-on-error t) can be really your friend(Continue reading)It helped to spot two errors in my site-start.el which i hardly understand: 1. The diminish mode can not be required when its byte-compiled. That's okay because i just leave it as it is. 2. flyspell-mode is just not working
See my other posting regardint this topic. I'm activating flyspell-mode using a construction like Enrico did, i.e. i add a function to the LaTeX-mode-hook which contains (flyspell-mode 1) and exactly there i get the error 'Expected language \"en\" but got \"de\"."'. I don't understand why this happens. I will have a close look at flyspells Costumize section maybe i changed something at fforgot about it?! At the moment i just don't get what this error means. Changing dicts is possible so why is he so upset about it? Confused Martin -- -- Take my word for it, the silliest woman can manage a clever man, but it
RSS Feed4 | |
|---|---|
7 | |
21 | |
8 | |
9 | |
4 | |
12 | |
6 | |
1 | |
30 | |
17 | |
9 | |
7 | |
28 | |
28 | |
43 | |
19 | |
32 | |
65 | |
169 | |
76 | |
37 | |
13 | |
11 | |
41 | |
20 | |
37 | |
79 | |
44 | |
44 | |
70 | |
65 | |
33 | |
55 | |
70 | |
109 | |
89 | |
58 | |
62 | |
5 | |
20 | |
16 | |
54 | |
31 | |
99 | |
107 | |
16 | |
19 | |
30 | |
60 | |
92 | |
133 | |
37 | |
144 | |
95 | |
88 | |
51 | |
89 | |
144 | |
79 | |
33 | |
68 | |
50 | |
131 | |
72 | |
66 | |
90 | |
114 | |
79 | |
104 | |
157 | |
104 | |
86 | |
48 | |
27 | |
104 | |
77 | |
33 | |
109 | |
38 | |
45 | |
71 | |
37 | |
64 | |
75 | |
92 | |
109 | |
96 | |
144 | |
166 | |
107 | |
174 | |
110 | |
159 | |
141 | |
245 | |
257 | |
54 | |
67 | |
36 | |
115 |
