Hans Hagen wrote:
> Mojca Miklavec wrote:
>
> >(are Greek quotations treated specially or what is this doing in regi-grk?)
> >% 00BB RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
> >\rightguillemot vs. \greekrightquot vs. \prewordbreak\rightguillemot
> >(in my point of view the last one may be better,
On 12/23/05, Hans Hagen <[EMAIL PROTECTED]> 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, VIS
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 -)
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www
Mojca Miklavec wrote:
I thought so. But the issue is not a matter of font designers, but of
underlying software. If TeX can't "unget" a character and replace it
with the accented one, you can't ask font designers to add dozens of
ligatures. Knuth didn't write TeX with Unicode conventions in min
Taco Hoekwater wrote:
> Mojca Miklavec wrote:
> >>\NC 0300 COMBINING GRAVE ACCENT \NC \textgrave \NC \NR
> >>\NC 0309 COMBINING HOOK ABOVE \NC \texthookabove \NC \NR
> >>\NC 0303 COMBINING TILDE\NC \texttilde \NC \NR
> >>\NC 0301 COMBINING ACUTE ACCENT \NC \texta
Taco Hoekwater wrote:
>
> >> Should \textellipsis be used for "2026 HORIZONTAL ELLIPSIS"
>
> Yes. But on the baseline, so:
OK, thanks.
>\definecharacter textellipsis {\periods\relax}
So perhaps fix the unic-032.tex again then.
> I believe there is a four-dot leader in unicode as well, b
Mojca Miklavec wrote:
\NC 0300 COMBINING GRAVE ACCENT \NC \textgrave \NC \NR
\NC 0309 COMBINING HOOK ABOVE \NC \texthookabove \NC \NR
\NC 0303 COMBINING TILDE\NC \texttilde \NC \NR
\NC 0301 COMBINING ACUTE ACCENT \NC \textacute \NC \NR
\NC 0323 COMBIN
Hans Hagen wrote:
PLEASE FIX:
in enco-def.tex replace \cdots by something (\dots, I suppose, but I'm
not sure)
\definecharacter textellipsis {\mathematics\cdots}
(I guess this "bug" was the reason for changing some definitions in
regimes/encodings elsewhere.)
Should \textellipsis be use
Mojca Miklavec wrote:
\defineregimesynonym[windows-1250][cp1250]
the synonym features is already in the kernel; the following patch to
regi-ini will permit file name synonyms, so
\definefilesynonym[regi-win][...]
patch:
\def\douseregime#1% nearly identical to encoding
{\doifundefined{
Mojca Miklavec wrote:
I'll send the files (full content is already on my page), but I need
to know how to split/group them (I guess it would be a bad idea to
have one file for each encoding). Should there be one file for
iso-8859 and one for windows encodings? What about those regimes that
are a
Taco Hoekwater wrote:
>
> Here's what I can come up with. At least a few are acceptable, like the
> horizontal bar. \textnumero exists, but is only reachable in cyrillic
> encodings (fixable, I guess?), and the greek & vietnamese accents
> are also only usable in the correct encoding. I've used the
Taco Hoekwater wrote:
\definecharacter texthorizontalbar {{--\kern 0pt--}}
\definecharacter textdong {\underbar{\dstroke}}
ok, i added those to enco-def.tex (end of file:)
\startencoding[\s!default]
\definecharacter texthorizontalbar {{--\kern\zeropoint--}}
\definecharacter textdon
Here's what I can come up with. At least a few are acceptable, like the
horizontal bar. \textnumero exists, but is only reachable in cyrillic
encodings (fixable, I guess?), and the greek & vietnamese accents
are also only usable in the correct encoding. I've used the \text...
versions of the acce
Hans Hagen wrote:
> Mojca Miklavec wrote:
> >Taco Hoekwater wrote:
> >
> >>New features since 2005.12.18:
> >>
> >>* Support for the latin-9 regime (latin-1 + euro)
> >>
> >
> >There are some more (automatically generated) regime definitions at
> >http://pub.mojca.org/tex/enco/contextbase/
> >(only
14 matches
Mail list logo