ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Petr Ferdus <pferdus@vertigo.fme.vutbr.cz>
Cc: ntg-context@ntg.nl
Subject: Re: unicode in bookmarks / unicode searching support
Date: Tue, 28 Nov 2000 17:04:33 +0100 (CET)	[thread overview]
Message-ID: <Pine.BSF.3.96.1001128164649.28022A-100000@vertigo.fme.vutbr.cz> (raw)
In-Reply-To: <3.0.6.32.20001128130836.019a4be0@pop.wxs.nl>

On Tue, 28 Nov 2000, Hans Hagen wrote:
> Well, it depends on how dependent this is of an encoding vector. I think
> that in that case we need some specific unicode def section per encoding
> vector. I did some tests and i think it can be implemented without
> noticable overhead. You may test the attached file [just include it on top
> of your doc] and don't include obj's manually. This test hack may also be
> of interest to polish etc users i think. 
Unfortunatelly, including unitest.tex did not help. Resulting file 
(test04contex.pdf) has accented searchable just scaron, zcaron, yacute,
aacute, iacute, eacute, oacute and uacute characters together with
uppercase relatives. File generated by older "method" (test04plain.pdf)
has all accented characters seachable/copyable. 
all files located at:
http://vertigo.fme.vutbr.cz/~pferdus/context/
Which results did you get with inclusion of unitest.tex?

> Are there more such predefined lists of unicode mappings? 
I am not aware of others. Perhaps Ondrej Koala Vacha <koala@fi.muni.cz>
might know more about it.

Thanks.
Peter


  reply	other threads:[~2000-11-28 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSF.3.96.1001127035447.9316A-100000@vertigo.fme.vutbr .cz>
2000-11-27 10:20 ` unicode in bookmarks Hans Hagen
2000-11-27 15:28 ` Hans Hagen
2000-11-28 10:53   ` Petr Ferdus
     [not found]   ` <Pine.BSF.3.96.1001128111339.22864A-100000@vertigo.fme.vutb r.cz>
2000-11-28 11:21     ` Hans Hagen
2000-11-28 12:08     ` unicode in bookmarks / unicode searching support Hans Hagen
2000-11-28 16:04       ` Petr Ferdus [this message]
     [not found]       ` <Pine.BSF.3.96.1001128164649.28022A-100000@vertigo.fme.vutb r.cz>
2000-11-28 17:34         ` Hans Hagen
2000-11-28 22:46           ` Petr Ferdus
     [not found]           ` <Pine.BSF.3.96.1001128223054.9364A-100000@vertigo.fme.vutbr .cz>
2000-11-29  8:54             ` Hans Hagen

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=Pine.BSF.3.96.1001128164649.28022A-100000@vertigo.fme.vutbr.cz \
    --to=pferdus@vertigo.fme.vutbr.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).