From: VnPenguin <vnpenguin@gmail.com>
Subject: Re: Character names
Date: Fri, 23 Dec 2005 22:33:08 +0100 [thread overview]
Message-ID: <e5d3f2650512231333o20dc7601x823b35115df053f2@mail.gmail.com> (raw)
In-Reply-To: <43AC0C10.2000605@wxs.nl>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On 12/23/05, Hans Hagen <pragma@wxs.nl> wrote:
> Mojca Miklavec wrote:
>
> >I'll consider this as "leave Windows Vietnamese encoding unsupported"
> >(they have two other encodings anyway).
> >
> >
> indeed (also, i never heard vnpenquin ask for it -)
>
Hi all,
In fact, VnTeX supports UTF-8, VISCII, TCVN, VPS. So it would be nice
if ConTeXt could do the same :) In reality, the charset UTF-8 becomes
a standard in Vietnam, and other charsets (VISCII, VPS, TCVN) are less
and less used. For me, I used always UTF-8 for all my documents here
(ConTeXt, OpenOffice, HTML, MySQL data,...).
Thank you for your wonderful work,
Merry Christmas !
--
http://vnoss.org
Vietnamese Open Source Software Community
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
prev parent reply other threads:[~2005-12-23 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 14:19 Character names (was: Context 2005.12.19 released) Mojca Miklavec
2005-12-21 16:17 ` Taco Hoekwater
2005-12-21 18:09 ` Hans Hagen
2005-12-23 1:00 ` Mojca Miklavec
2005-12-23 9:44 ` Character names Hans Hagen
2005-12-23 12:29 ` Taco Hoekwater
2005-12-23 12:48 ` Mojca Miklavec
2005-12-25 23:48 ` Mojca Miklavec
2005-12-23 10:31 ` Hans Hagen
2005-12-23 12:36 ` Taco Hoekwater
2005-12-23 13:39 ` Mojca Miklavec
2005-12-23 14:18 ` Taco Hoekwater
2005-12-23 14:39 ` Hans Hagen
2005-12-23 21:33 ` VnPenguin [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=e5d3f2650512231333o20dc7601x823b35115df053f2@mail.gmail.com \
--to=vnpenguin@gmail.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).