From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: unicode in bookmarks
Date: Fri, 01 Dec 2000 18:33:14 +0100 [thread overview]
Message-ID: <3.0.6.32.20001201183314.008ee4a0@pop.wxs.nl> (raw)
In-Reply-To: <Pine.BSF.3.96.1001201154014.25304E-100000@vertigo.fme.vutb r.cz>
At 05:52 PM 12/1/00 +0100, Petr Ferdus wrote:
>On Wed, 29 Nov 2000, Hans Hagen wrote:
>
results. (perhaps now comes the time to extend and apply code
>from your first reply, with note example, to proces string feeded to
>bookmark). Is it correct? Or did unitable changed situation somehow?
For that, the unicode list should be extended, since i defined only a few
chars,
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next parent reply other threads:[~2000-12-01 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.6.32.20001129091246.01766810@pop.wxs.nl>
[not found] ` <Pine.BSF.3.96.1001201154014.25304E-100000@vertigo.fme.vutb r.cz>
2000-12-01 17:33 ` Hans Hagen [this message]
2000-12-05 10:58 ` Petr Ferdus
2000-12-11 19:14 ` unicode in bookmarks - solved for now Petr Ferdus
[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-27 3:07 Petr Ferdus
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=3.0.6.32.20001201183314.008ee4a0@pop.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).