ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with Lua processing UTF8 substrings
Date: Wed, 1 Feb 2012 21:35:38 +0100	[thread overview]
Message-ID: <20120201203538.GA11795@phlegethon> (raw)
In-Reply-To: <4F299DD8.7020307@gyza.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1749 bytes --]

On 2012-02-01 21:17, Jaroslav Hajtmar wrote:
> Hello Philipp.
> Thanx very much for very quick and perfect help.
> Is there any manual or source, where I can read these (and next and
> similar) information?

I’m sorry I have to disappoint you but the utf library is
documented only in the source.[1] Luckily it covers all the
functionality of the native string library, thus its usage should
be equivalent except that it works for utf sequences as well. If
you know some German there’s also a blog post by Patrick.[2]

The string.utfcharacters iterator is covered in luatexref-t.pdf.

Hope this helps
Philipp

[1] http://files.luaforge.net/releases/sln/slnunicode/1.1a
[2] http://www.luatex.de/2010/02/selene-unicode-bibliothek/?iframe=true


> 
> One more thanx
> Jaroslav Hajtmar
> 
> 
> 
> Dne 1.2.2012 21:05, Philipp Gesang napsal(a):
> >\def\mymacro#1{%
> >   \startluacode
> >     local utf = unicode.utf8
> >     local target = [==[\detokenize{#1}]==]
> >     for i=1, utf.len(target) do
> >       context(utf.sub(target,i,i)..", ")
> >     end
> >   \stopluacode%
> >}
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2012-02-01 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 19:26 Jaroslav Hajtmar
2012-02-01 20:05 ` Philipp Gesang
2012-02-01 20:17   ` Jaroslav Hajtmar
2012-02-01 20:35     ` Philipp Gesang [this message]
2012-02-01 20:38       ` Jaroslav Hajtmar

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=20120201203538.GA11795@phlegethon \
    --to=gesang@stud.uni-heidelberg.de \
    --cc=hajtmar@gyza.cz \
    --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).