unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Martin Ivanov <tramni@abv.bg>
Subject: emacs cyrillic
Date: Tue, 7 Nov 2006 15:03:31 +0200 (GMT+02:00)	[thread overview]
Message-ID: <263262129.142041162904611093.JavaMail.nobody@mail03.abv.bg> (raw)

Hello again!

I changed LANG fron en.us to bg_BG. Then I started emacs with the option -q and opened a file previously saved with cyrillic text. It was not displayed correctly. Then I started emacs without the option -q and the file was diplayed as it should have been. Obvoiusly the bulgarian.el file is necessary, I do not know why. This is the complete list of choices I have when I choose to change the ispell dictionary:

american			   brasileiro
british				   castellano
castellano8			   czech
dansk				   default
deutsch				   deutsch8
english				   esperanto
esperanto-tex			   francais
francais-tex			   francais7
german				   german8
italiano			   nederlands
nederlands8			   norsk
norsk7-tex			   polish
portugues			   russian
slovak				   svenska

What can be done so that bulgarian appears in that menu? 
If I choose something different from american or english, emacs complains it cannot find the respective .hash file in /usr/lib/ispell. And it is ok, since the contents of /usr/lib ispell is :

american.hash@    bg.multi       bulgarian.aff    bulgarian.kbd  english.hash@
americanmed.hash  bg.rws         bulgarian.alias  cp1251.dat
bg.dat            bg_phonet.dat  bulgarian.hash   english.aff

I am sorry if I bore you, but I wish to be as clear as possible with the risk of repeating things.
Besides, there is another point. If I run ispell american in flyspell mode on a file that contains both cyrillic and latin words, only the latin words are underlined. the cyrillic word are not considered mistake, which is strange to me.

I am so thankful to you for your responsiveness.

Regards,
Martin


 >-------- Оригинално писмо --------
 >От:  Peter Dyballa <Peter_Dyballa@Web.DE>
 >Относно: Re: emacs cyrillic
 >До: Martin Ivanov <tramni@abv.bg>
 >Изпратено на: Вторник, 2006, Ноември 7 12:49:05 GMT+02:00
 >----------------------------------
 >
 >
 >Am 07.11.2006 um 10:46 schrieb Martin Ivanov:
 >
 >> without the bulgarian.el file, I canot set the language environment  
 >> to "Bulgarian standard, I cannot at all write cyrillic. A have the  
 >> LANG variable on my system. Concerning bulgarian it says:
 >> bg_BG
 >> bg_BG.utf8
 >
 >Usually 'locale -a | grep -i bg' should display all choices you have  
 >for Bulgarian. Once in the shell environment LANG or LC_CTYPE are  
 >set, GNU Emacs reads them and sets itself to handle this world. There  
 >is not much Elisp code needed, it's all already written.
 >
 >Bulgarian.el is similar in that purpose, but restricted to one  
 >particular environment. Since I have no Bulgarian environment here  
 >and no Slackware, not even a PC, I think I cannot be of more help in  
 >this particular issue.
 >
 >> "ispell -vv" as attachment.
 >
 >LIBDIR = "/usr/lib/ispell"
 >
 >is the important line. So your system seems to be ready. If it  
 >continues to fail, then some Elisp code must be wrong. You can launch  
 >GNU Emacs with the options -q or -Q, which do not load personal or  
 >all initialisation files. You should try to launch GNU Emacs with  
 >either of these options and see whether you can setup for using  
 >ispell and the Bulgarian dictionary. If this has success, you can try  
 >to determine which file is faulty, by commenting load or require  
 >statements. In the faulty Elisp file you can comment halves to see  
 >where the bug happens. And by commenting one half of this half  
 >successively, step by step, you might be able to determine the faulty  
 >line of code.
 >
 >If it fails to use the Bulgarian dictionary *without* personal or  
 >system initialisation files, then there is some evidence of a bug in  
 >GNU Emacs and you should choose from the Help menu the "Send Bug  
 >Report..." item and write a bug report. You can invoke Emacs as  
 >'emacs --help' so see the meaning of the options it supports.
 >
 >
 >--
 >Greetings
 >
 >   Pete
 >
 >If my theory of relativity is proven successful, Germany will claim  
 >me as a German, and France will declare that I am a citizen of the  
 >world. Should my theory prove untrue, France will say that I am a  
 >German, and Germany will declare that I am a Jew.
 >                                                 -- Albert Einstein,  
 >1929
 >
 >
 >

-----------------------------------------------------------------
Survivor BG. Оцеляването продължава на www.survivor.btv.bg 

             reply	other threads:[~2006-11-07 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 13:03 Martin Ivanov [this message]
2006-11-07 23:47 ` emacs cyrillic Kevin Rodgers
     [not found] <2032892203.462561162683925062.JavaMail.nobody@mail08.abv.bg>
2006-11-05 15:03 ` Peter Dyballa
2006-11-05 16:54   ` Eli Zaretskii
2006-11-05 20:29     ` Peter Dyballa
  -- strict thread matches above, loose matches on Subject: below --
2006-11-04 16:38 Martin Ivanov
2006-11-04 20:08 ` Peter Dyballa
2006-11-05  1:44   ` ken
2006-11-05  8:53     ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=263262129.142041162904611093.JavaMail.nobody@mail03.abv.bg \
    --to=tramni@abv.bg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).