From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Update ispell-dictionary to text language
Date: Fri, 15 Jan 2010 09:55:57 +0100 [thread overview]
Message-ID: <876373wxuq.fsf@mundaneum.com> (raw)
In-Reply-To: 0D07D866-37AB-419D-BB59-61DC376681FB@gmail.com
Hi Carsten,
Carsten Dominik wrote:
> On Jan 13, 2010, at 11:20 AM, Sébastien Vauban wrote:
>> Benjamin Andresen wrote:
>>> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>>>
>>>> Here my proposal (and my very first self-written chunk of ELisp code) for
>>>> switching to the right language for ispell, upon reading the contents of
>>>> the meta-tag `LANGUAGE'.
>>>
>>> I think using File Variables are better for this. For no particular reason
>>> except they are standardized and don't require any additional code in Org
>>> Mode.
>>> (info "(emacs)Specifying File Variables")
>>> # -*- ispell-local-dictionary: "german" -*-
>>
>> I know them [...] BUT there is a *language specification* in the Org
>> template [...] AND it is *used by Org* (at least for the HTML export, and
>> for LaTeX as well I think -- or, in any case, it should use it).
>>
>> Thus, I try to avoid declaring which language is used in the buffer at two
>> different spots, because we can change one and forget to change the other.
>>
>> Therefore, I would like to keep only one language declaration (the one of
>> the Org template, in this case), and get Emacs follow it.
>>
>> Does this make sense?
>
> I have seen this thread and I am still contemplating what
> to do with it.
My arguments are:
- We have a language specification in the Org template
- That should be used during the export to HTML (DONE)
- That should be used during the export to LaTeX (TODO)
- That should be used for editing the buffer in the right language (TODO/DONE,
see my proposal)
I'm quite against /mixing language declarations/:
- in the Org template *and*
- in buffer local variables.
Of course, we could imagine the other way around: using the value of
`ispell-local-dictionary' for the 3 objectives (edition in correct language,
correct setting for generated HTML, correct setting for generated LaTeX). It'd
be as good for me.
> More input and opinions would be welcome.
So do I! ;-)
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-01-15 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 11:27 Update ispell-dictionary to text language Sébastien Vauban
2010-01-11 15:31 ` Benjamin Andresen
2010-01-13 10:20 ` Sébastien Vauban
2010-01-15 7:14 ` Carsten Dominik
2010-01-15 8:55 ` Sébastien Vauban [this message]
2010-01-15 10:22 ` Torsten Wagner
2010-02-21 8:25 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=876373wxuq.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).