[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#635382: [tex-live] new release of latex-unicode



On 2012-04-18 at 17:35:55 +0300, Wolfgang Jeltsch wrote:

 > Am Mittwoch, den 11.04.2012, 23:06 +0200 schrieb Reinhard Kotucha:
 > > On 2012-04-11 at 15:47:06 +0900, Norbert Preining wrote:
 > > > Dear Wolfgang,
 > > > 
 > > > I was taking a look at your darcs repository and compared it
 > > > with what is currently available on the CTAN. Besides the
 > > > addition of .dtx/.ins files and some more scripts and text
 > > > files, there are some changes:
 > > > unicode/data/uni-1.def:
 > > > -\uc@dclc{416}{default}{\OHORN}%
 > > > -\uc@dclc{417}{default}{\ohorn}%
 > > > +\uc@dclc{416}{default}{\horn O}%
 > > > +\uc@dclc{417}{default}{\horn o}%
 > > > 
 > > > and
 > > > -\uc@dclc{431}{default}{\UHORN}%
 > > > -\uc@dclc{432}{default}{\uhorn}%
 > > > +\uc@dclc{431}{default}{\horn U}%
 > > > +\uc@dclc{432}{default}{\horn u}%
 > >
 > > […]
 > > 
 > > Does the change "\OHORN" ==> "\horn O" have any impact on what
 > > Hàn Thế Thành describes in his file "vn-min.pdf" (texdoc vn-min)
 > > when people are using ucs?
 > 
 > Unfortunately, I didn’t find anything in vn-min.pdf that is related
 > to ucs. What remark do you mean?

If someone uses control sequences like \ohorn in macro packages
already, does he have to change them to \horn o when using ucs?  The
advantage of using such control sequences in macro packages is to
allow the user to use any input encoding in the main document.  From

  texmf-dist/tex/latex/vntex/vncaps.tex :

  \providecommand\captionsvietnam{%
    \def\prefacename{L\`\ohorn i n\'oi \dj\`\acircumflex u}%
    \def\refname{T\`ai li\d\ecircumflex u}%
    \def\abstractname{T\'om t\'\abreve t n\d\ocircumflex i dung}%
    \def\bibname{T\`ai li\d\ecircumflex u tham kh\h{a}o}%
    \def\chaptername{Ch\uhorn \ohorn ng}%

Will this still work or does ucs require now (last line)

    \def\chaptername{Ch\horn u \horn o ng}%
 
?  That would be an incompatibility with vncaps.tex.
 
 > Actually, the changes in the mapping of the horn characters were
 > done by Dominique Unruh before I became the maintainer of the
 > unicode package. I took the version without the horn change from
 > CTAN, and the version with the horn change from Dominique’s website
 > (which is now defunct).
 > 
 > I have no idea what this change was for. And while I have found
 > references to \OHORN, \ohorn, \UHORN, and \uhorn in The
 > Comprehensive LateX Symbol List, I haven’t found references to
 > \horn. So maybe, it is best if I just revert this change.
 > 
 > What do you think?

Since I can't oversee the impact of the change, it's better to test
it.  VnTeX provides a bunch of test files in the directory

  texmf-dist/source/generic/vntex/tests

.  You can run

  pdflatex test-babel.tex

twice within this directory and look at section 1.4 (utf8x).  BTW,
\usepackage{vietnam} implicitly loads vncaps.tex, hence these \...name
macros containing LICR are tested as well.
 
Maybe it's advisable to repeat the test with all the other sections
and LaTeX's utf8 commented out, just in order to make sure that the
ucs test doesn't see control sequences defined by other packages.

If you have any suggestions regarding the test files, please let me
know.  Admittedly I didn't spent much time on ucs support because at
the time the files were created, usc.sty was not widely spread
(hence \IfFileExists{ucs.sty}) but already unmaintained by Dominique.
Since you are maintaining ucs now, I certainly have to pay more
attention to it.

Regards,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha                                      Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover                              mailto:reinhard.kotucha@web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------



Reply to: