ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context.labeltext(...)
Date: Tue, 05 Jul 2011 09:22:20 +0200	[thread overview]
Message-ID: <4E12BBAC.2000705@wxs.nl> (raw)
In-Reply-To: <20110704165314.GA6145@khaled-laptop>

On 4-7-2011 6:53, Khaled Hosny wrote:
> On Mon, Jul 04, 2011 at 06:20:37PM +0200, luigi scarso wrote:
>> On Mon, Jul 4, 2011 at 6:05 PM, Willi Egger<w.egger@boede.nl>  wrote:
>>> Hi Luigi,
>>>
>>> hm, did not know this one. Still I can not see that this is going to
>>> fit in my situation. I refer to may other mail I sent a minute ago.
>>> - The thing is, that the document I am building should be
>>> multilingual and therefore I need at the lua-end the lowercase text
>>> which should be made first-letter-uppercase at the moment it is
>>> typeset.
>> In the first email you talked about a generic label. Uppercase /lower
>> case are unicode sensitive; as Wolfgang already wrote
>> string.lower(..) and string.upper(..) can help , but they depend on
>
> unicode.utf8.lower()/upper() are a better choice for non-ASCII text.
>
> (I still believe the default string manipulation functions should be
> Unicode aware by default, and the 8-bit ones should be an alternative,
> not the other way around).

you can just rename/remap them if needed; swapping stock lua and unicode 
functions would render regular lua manuals/tutorials useless and also 
make lua 8-bit dirty

(local lower = utf.lower at the top of a file is enough to get what you 
want)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2011-07-05  7:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 15:02 context.labeltext(...) Willi Egger
2011-07-04 15:41 ` context.labeltext(...) Wolfgang Schuster
2011-07-04 16:00   ` context.labeltext(...) Willi Egger
2011-07-04 16:12     ` context.labeltext(...) Wolfgang Schuster
2011-07-04 15:54 ` context.labeltext(...) luigi scarso
2011-07-04 16:05   ` context.labeltext(...) Willi Egger
2011-07-04 16:14     ` context.labeltext(...) Wolfgang Schuster
2011-07-04 16:20     ` context.labeltext(...) luigi scarso
2011-07-04 16:53       ` context.labeltext(...) Khaled Hosny
2011-07-04 17:02         ` context.labeltext(...) Wolfgang Schuster
2011-07-05  7:22         ` Hans Hagen [this message]

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=4E12BBAC.2000705@wxs.nl \
    --to=pragma@wxs.nl \
    --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).