From: Ciro Soto <ciro@kavyata.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: spanish tilde-n lost
Date: Sun, 28 Jun 2009 20:19:23 -0400 [thread overview]
Message-ID: <297ee2eb0906281719o69db9e70w68493e948f70aa8f@mail.gmail.com> (raw)
In-Reply-To: <4A477EDF.3060106@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2093 bytes --]
Thank you all.
This is the feedback of your recommendations:
\enableregime[utf]
didn't work.
typing just ñ
worked fine.
\defineaccent ~ n {\ntilde}
worked using \~n and
This last solution is the one I was looking for because my keyboard has no ñ
thanks
Ciro
-- Links of your interest:
http://www-personal.engin.umd.umich.edu/~cirosoto/
http://www.TheGuitarMakerExploration.com
http://www.myspace.com/sotoaguirre
On Sun, Jun 28, 2009 at 10:31 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Mojca Miklavec wrote:
>
>> On Sun, Jun 28, 2009 at 01:16, Ciro Soto wrote:
>>
>>> Hi all,
>>> I finally got around the intallation of context minimals. Thank you for
>>> those who helped. I ran my old tex files (in spanish) and found that \~n
>>> is
>>> not working now.
>>> It should create an n with a tilde on top, but what happens is that there
>>> is
>>> no
>>> letter printed at all.
>>>
>>
>> I guess that you are asking about MKIV since it seems to work OK in MKII.
>>
>> What is the fix for this? Any switch?
>>> (I know I could use \char but I am looking for a more elegant solution)
>>>
>>
>> The most elegant solution is to use just ñ and it should work out of
>> the box there.
>> But still I would ask Hans to add the following line to enco-ini.mkiv:
>>
>> \defineaccent ~ N {\Ntilde} \defineaccent ~ n {\ntilde}
>>
>> You can try to modify the file yourself, then run "context --make" and
>> it should start working.
>>
>> (I always thought that these lines were "auto-generated" from Unicode
>> data on the fly.)
>>
>
> not this one; the ntild probably got lost at some point during cleaning up
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 3238 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-29 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 23:16 Ciro Soto
2009-06-28 5:30 ` thfl
2009-06-28 6:09 ` Peter Münster
2009-06-28 6:10 ` thfl
2009-06-28 12:03 ` Mojca Miklavec
2009-06-28 14:31 ` Hans Hagen
2009-06-29 0:19 ` Ciro Soto [this message]
2009-06-29 6:06 ` Peter Münster
2009-06-29 9:15 ` Mojca Miklavec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=297ee2eb0906281719o69db9e70w68493e948f70aa8f@mail.gmail.com \
--to=ciro@kavyata.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).