Re: [XeTeX] solved partially
On Mon, Oct 24 2022 at 15:35 GMT, Guido Herzog wrote: > I think it's not about the variation selector, > but about the variant form of a character. ??? [...] > - > Von: XeTeX im Auftrag von > Janusz S. Bień > Gesendet: Sonntag, 16. Oktober 2022 16:47 > An: XeTeX discussion > Betreff: [XeTeX] solved partially (was: How to print a variation selectors?) > > On Sun, Oct 16 2022 at 17:56 +02, Janusz S. Bień wrote: > [...] > What are other, more commonly used, fonts with VS1 glyphs? My post was definitely about a variation selector *glyph*. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] [EXT] solved partially
On Mon, Oct 17 2022 at 10:54 +02, Stefan Solbrig wrote: > Hi, > In XeTeX, you can also use \XeTeXcharglyph to get the (font dependant) glyph > number for the character code. Thanks! Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] solved partially
On Sun, Oct 16 2022 at 21:25 +02, Ulrike Fischer wrote:
Thank you very much for your comments!
> Am Sun, 16 Oct 2022 18:47:30 +0200 schrieb Janusz S. Bień:
>
>> On Sun, Oct 16 2022 at 17:56 +02, Janusz S. Bień wrote:
>>
>> Frank Mittelbach was kind enough to provide me with the relevant information:
>>
>> On Sun, Oct 16 2022 at 9:21 -07, Frank Mittelbach wrote:
>>> I checked. In Unicode this slot is default-ignorable and both XeTeX
>>> and LuaTeX do not print glyphs with that attribute (probably because
>>> the aren't not meant for printing).
>>>
>>> In luaTeX (but not in XeTeX I think) you can change this behavior.
>>
>> So the questions left are:
>>
>> Is it really impossible to do it in XeTeX?
>
> With lualatex you can force the glyph with Renderer=base:
>
> \documentclass{article}
> \usepackage{fontspec}
> \setmainfont{Noto Sans Manichaean}[Renderer=Base]
Or
\setmainfont[RawFeature={-invisible}]{Noto Sans Manichaean}
(pointed to me by Frank Mittelbach)
which refers directly to the Unicode character property discussed in
L2/02-368 (http://www.unicode.org/L2/L2002/02368-default-ignorable.pdf)
and https://github.com/latex3/luaotfload/issues/63.
> \begin{document}
> \thispagestyle{empty}
>
> \char"FE00
>
> \end{document}
>
> With xelatex you can use the glyph slot:
>
> \documentclass{article}
> \usepackage{fontspec}
> \setmainfont{Noto Sans Manichaean}\begin{document}
> \thispagestyle{empty}
>
> \XeTeXglyph58
That's the command I need! Either I haven't noticed it at all or forgot
about it :-(
>
> \end{document}
>
> The number 58 is font dependant (I found this one by looking in the
> font cache file created by lualatex)
Looks like it can be found in the ttx output in *.GlyphOrder.ttx,
e.g. .
Thanks once again!
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
[XeTeX] solved partially (was: How to print a variation selectors?)
On Sun, Oct 16 2022 at 17:56 +02, Janusz S. Bień wrote: Frank Mittelbach was kind enough to provide me with the relevant information: On Sun, Oct 16 2022 at 9:21 -07, Frank Mittelbach wrote: > I checked. In Unicode this slot is default-ignorable and both XeTeX > and LuaTeX do not print glyphs with that attribute (probably because > the aren't not meant for printing). > > In luaTeX (but not in XeTeX I think) you can change this behavior. So the questions left are: Is it really impossible to do it in XeTeX? What are other, more commonly used, fonts with VS1 glyphs? Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] How to print a variation selectors?
On Sun, Oct 16 2022 at 17:40 +02, Janusz S. Bień wrote:
> On Fri, Oct 14 2022 at 8:16 +02, Janusz S. Bień wrote:
>> Hi!
>>
>> I just noticed, to my pleasant surprise, that my Emacs renders VS1 with
>> the glyph used in the standard; the glyph is taken from Noto Sans
>> Manichaean Regular (no idea why Emacs selected just this very font).
>>
>> Actually I was looking for a font which contains glyphs for variation
>> selectors, so I tried to print it. As this did not work, I tried check
>> whether the VS1 works in the intended context, i.e. with e.g. MANICHAEAN
>> LETTER DALETH, and I am quite confused --- sometimes it works and
>> sometimes it doesn't.
>>
>> Please have a look at the enclosed examples. I will appreciate very much
>> your comments.
>
> I just noticed that in the list archive the first attachment looks
> strange, so I repeat it inline:
Unfortunately it doesn't help. So here is just plain text:
--8<---cut here---start->8---
\documentclass{standalone}
\usepackage{fontspec}
\setmainfont{Noto Sans Manichaean}
\begin{document}
\thispagestyle{empty}
\char"10AC5
\char"10AC5 ︀
\char"10AC5\char"FE00
︀
\char"FE00
fe00
\end{document}
%%% Local Variables:
%%% coding: utf-8-unix
%%% mode: latex
%%% TeX-master: t
%%% TeX-PDF-mode: t
%%% TeX-engine: xetex
%%% End:
--8<---cut here---end--->8---
>
>
> Regards
>
> JSB
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Re: [XeTeX] How to print a variation selectors?
On Fri, Oct 14 2022 at 8:16 +02, Janusz S. Bień wrote:
> Hi!
>
> I just noticed, to my pleasant surprise, that my Emacs renders VS1 with
> the glyph used in the standard; the glyph is taken from Noto Sans
> Manichaean Regular (no idea why Emacs selected just this very font).
>
> Actually I was looking for a font which contains glyphs for variation
> selectors, so I tried to print it. As this did not work, I tried check
> whether the VS1 works in the intended context, i.e. with e.g. MANICHAEAN
> LETTER DALETH, and I am quite confused --- sometimes it works and
> sometimes it doesn't.
>
> Please have a look at the enclosed examples. I will appreciate very much
> your comments.
I just noticed that in the list archive the first attachment looks
strange, so I repeat it inline:
\documentclass{standalone}
\usepackage{fontspec}
\setmainfont{Noto Sans Manichaean}
\begin{document}
\thispagestyle{empty}
\char"10AC5
\char"10AC5 ︀
\char"10AC5\char"FE00
︀
\char"FE00
fe00
\end{document}
%%% Local Variables:
%%% coding: utf-8-unix
%%% mode: latex
%%% TeX-master: t
%%% TeX-PDF-mode: t
%%% TeX-engine: xetex
%%% End:
Regards
JSB
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
[XeTeX] How to print a variation selectors?
Hi!
I just noticed, to my pleasant surprise, that my Emacs renders VS1 with
the glyph used in the standard; the glyph is taken from Noto Sans
Manichaean Regular (no idea why Emacs selected just this very font).
Actually I was looking for a font which contains glyphs for variation
selectors, so I tried to print it. As this did not work, I tried check
whether the VS1 works in the intended context, i.e. with e.g. MANICHAEAN
LETTER DALETH, and I am quite confused --- sometimes it works and
sometimes it doesn't.
Please have a look at the enclosed examples. I will appreciate very much
your comments.
\documentclass{standalone}
\usepackage{fontspec}
\setmainfont{Noto Sans Manichaean}
\begin{document}
\thispagestyle{empty}
\char"10AC5
\char"10AC5 ︀
\char"10AC5\char"FE00
︀
\char"FE00
fe00
\end{document}
%%% Local Variables:
%%% coding: utf-8-unix
%%% mode: latex
%%% TeX-master: t
%%% TeX-PDF-mode: t
%%% TeX-engine: xetex
%%% End:
VS1.pdf
Description: Adobe PDF document
VSsample.pdf
Description: Adobe PDF document
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?
On Sat, Aug 21 2021 at 15:20 +01, Philip Taylor (HI) wrote: > Ulrike Fischer wrote: > > With a current texlive you can use albatross to find out which fonts > on your system support this > >albatross -d 0xFFFD > > I appreciate that this answer may have been targetted solely at Doug McKenna, > but in the general case it does not work. Here, using TeX Live 2021 under > Windows 7 Ultimate, the command "albatross" is unknown — It's also absent in all verions of Debian, including testing, unstable and experimental. I've just downloaded it from CTAN (I had to circumvent a minor path problem). Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?
On Sat, Aug 21 2021 at 10:48 +02, Ulrike Fischer wrote: > Am Fri, 20 Aug 2021 19:45:37 -0600 (MDT) schrieb Doug McKenna: > >> Using XeTeX, I want to typeset a LaTeX document into a PDF file. The LaTeX >> source code in UTF-8 expressly includes the Unicode Replacement character (� >> = U+FFFD) > >> So ... What fixed-width and variable-width OpenType (or other) >> fonts, if any, are always distributed with TeX or TeXLive or >> whatever that one can rely upon to be available for placing this >> particular glyph in a final PDF file? What would be the correct >> incantation to doing so? > > With a current texlive you can use albatross to find out which fonts > on your system support this > >albatross -d 0xFFFD A nice replacement for fc-search-codepoint, as it accept also glyphs as the arguments. Best regard Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?
On Fri, Aug 20 2021 at 19:45 -06, Doug McKenna wrote: [...] > So ... What fixed-width and variable-width OpenType (or other) fonts, > if any, are always distributed with TeX or TeXLive or whatever that > one can rely upon to be available for placing this particular glyph in > a final PDF file? What would be the correct incantation to doing so? The question is which fonts you have installed on your system, not necessarily distributed with TeX. For checking whether you have an appropriate there are useful suggestions (Linux specific) at https://unix.stackexchange.com/questions/162305/find-the-best-font-for-rendering-a-codepoint The answer fc-list ':charset= ' is still valid, but the very usefull script fc-search-codepoint was written in Python2 so is unusable e.g. on Debian bullseyey. Another approach is to use "Font Support" at https://www.fileformat.info/. e.g. https://www.fileformat.info/info/unicode/char/fffd/fontsupport.htm Regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] strange case of overlapping graphics - the summary
Thank you very much for all the informations and comments! The culprit is definitely ddjvu: https://sourceforge.net/p/djvu/bugs/335/ Fortunately the output in the ppm format is correct, so after converting to png I can use it in my text. Once again thank you very much for you quick reaction to my problem! Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] strange case of overlapping graphics
On Thu, Jun 10 2021 at 11:04 -05, Herbert Schulz wrote:
>> On Jun 10, 2021, at 10:58 AM, Zdenek Wagner wrote:
>>
>> čt 10. 6. 2021 v 17:09 odesílatel Philip Taylor
>> napsal:
>>>
>>> In both Windows Preview and in Adobe Illustrator CC, the PNG file
>>> is roughly twice as tall (relative to its width) as it appears in
>>> the PDF.
>>> --
>> So this means that the PNG contains something strange which is
>> interpreted by some programs and ignored by other programs. Maybe
>> different vertical and horizontal resolutions? I do not have a tool to
>> analyze it further.
Tomorrow I will make more tests and submit the problem to ddjvu
author(s).
> Howdy,
>
> And
>
> \includegraphics[width=1.3cm]{Zaborowski_MBC_page19y42_a}
> \includegraphics[width=1.3cm]{Zaborowski_MBC_page19y42_a}
>
> works fine (not exactly the same size but that can be adjusted).
Yes. It's great you have found a way to circumvent the problem!
On the other hand this make the problem more misterious...
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Re: [XeTeX] strange case of overlapping graphics
On Thu, Jun 10 2021 at 10:40 -04, Michael Maxwell wrote: There is no overlapping if pdflatex ix used but the images are distorted, > > If it's the case that s.t. is wrong with the image (and okular, > gwenview and gimp are compensating somehow), could you import the > image into one of these other programs, then export it from there? As I said, the enclosed file was exported from Gimp. The same problem occurs when the original TIFF is converted with Imagemagick. If ddjvu is the culprit, then it does something so strange that the problem survives conversions and import/exports. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] strange case of overlapping graphics
On Thu, Jun 10 2021 at 16:23 +02, Zdenek Wagner wrote: > Yes, there is something strange. I can reproduce the behaviour with > xelatex. I prefer to stick to xelatex. > There is no overlapping if pdflatex ix used but the images > are distorted, see my result (after additional pdfcrop to remove the > white space on the page). ddjvu can generate pdf directly, but the results are distorted in a very similar way... > The picture itself looks fine in okular, gwenview as well as in gimp, > both "file" and "exiftool" show the right dimensions. > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml On Thu, Jun 10 2021 at 9:26 -05, Herbert Schulz wrote: [...] > Howdy, > > Also note that removing the height option from the first image will put the > images side by side. Yes, I can reproduce this. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
[XeTeX] strange case of overlapping graphics
Hi! Please have a look at the enclosed example. I suspect there is something wrong with the graphic file although no tool reports any problem. The file was exported from Gimp, the source was a TIFF file created by little known and little used ddjvu program (I used it for the first time just now). I will appreciate your help. Best regards Janusz <> -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] using character variants as RawFeature
On Sat, May 16 2020 at 20:05 +02, Ulrike Fischer wrote:
[...]
> You need a +, or alternatively use the fontspec key:
>
> \documentclass{article}
> \usepackage{fontspec}
> \setmainfont{JuniusX-Regular.ttf}[]
FYI: I had to skip the ttf extension, otherwise the font was not found
(it is in .local/share/fonts)
> \begin{document}
> \Huge
>
> 00f8
> \addfontfeature{RawFeature={+cv16=1}}
> 00f8
> \addfontfeature{CharacterVariant={16:2}}
> 00f8
Thank you very much!
The documentation of fontspec (section 3.1.2 on character variants) was
completely confusing for me because the notions of 'glyph number' was
not explained. I think actually this is a misnomer, perhaps 'feature
number' or something like this would be better.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Re: [XeTeX] using character variants as RawFeature
I forgot to include the list in my previous answer.
On Sat, May 16 2020 at 17:37 +00, Baker, Peter S (psb6m) wrote:
> Here's the syntax that worked for me:
>
> \usepackage{fontspec}
>
> \setmainfont{JuniusX}[RawFeature={+cv16=3}]
It works, thank you veru much.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
[XeTeX] using character variants as RawFeature
Hi!
I try to test the character variants introduced a few days ago to
JuniusX as the result of the following issue:
https://github.com/psb1558/Junicode-New/issues/3
Here is my last test:
--8<---cut here---start->8---
\documentclass{article}
\usepackage{fontspec}
\begin{document}
\fontspec[Path=../fonts/,RawFeature={cv16=4}]{JuniusX-Regular.ttf}
ø
\end{document}
--8<---cut here---end--->8---
I get the default variant of the letter and the log contains
"Unknown feature `cv16=4' in font."
What is wrong?
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Re: [XeTeX] FYI: \includegraphics and *.bb files
On Thu, May 16 2019 at 13:55 +02, Ulrike Fischer wrote: > Am Wed, 15 May 2019 05:36:36 +0200 schrieb Janusz S. Bień: > > >> The *.bb files was created for make4ht. Till recently they had no effect >> on XeLaTeX, > > They always had an effect on xelatex: if a bb-file is found it is > used. > >> now they cause scaling down (except a few, which is another >> mystery). >> >> What has changed? > > That's quite difficult to say from you information. My offer to upload a minimal example is still valid. > Perhaps you hadn't previously bb-files in the folder and now you have. It's possible. I think now I generated them by mistake, make4ht needs *.xbb. This does not explain why they are wrong or incorrectly used. > Or during your experiments with make4ht bb-files with smaller size > info's were created. I guess make4ht doesn't use them, but I may be wrong. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] FYI: \includegraphics and *.bb files
On Tue, May 14 2019 at 21:44 +02, Bruno Le Floch wrote: > On 5/14/19 21:15, Janusz S. Bień wrote: >> On Tue, May 14 2019 at 20:48 +02, Bruno Le Floch wrote: [...] > https://groups.google.com/forum/#!topic/comp.text.tex/iJcKNH9VgCE > > seems to have some related information The topic is similar but I don't think it is relevant to the problem. On Tue, May 14 2019 at 23:12 +02, Zdenek Wagner wrote: > I have never used *.bb files. The *.bb files was created for make4ht. Till recently they had no effect on XeLaTeX, now they cause scaling down (except a few, which is another mystery). What has changed? Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] FYI: \includegraphics and *.bb files
On Tue, May 14 2019 at 20:48 +02, Bruno Le Floch wrote: > On 5/14/19 08:50, Janusz S. Bień wrote: >> The paper was accepted and several days ago I prepared a final >> version. To my surprise almost all images was scaled down by >> XeLaTeX. The test shows the culprit is the presence of *.bb files. There >> are however some *.bb files which has no such side effect. >> >> All *.bb files were created by the same version of the same program, I >> don't see any essential difference between them. > > The difference may be in the image files themselves: some images declare > their bounding boxes and others not. I don't remember details but if > you can state what file-type the images have, this may help. All images are in the PNG format: --8<---cut here---start->8--- paginacja_1x.png: PNG image data, 2871 x 511, 8-bit gray+alpha, non-interlaced paginacja2-3.png: PNG image data, 352 x 324, 8-bit/color RGBA, non-interlaced paginacja5_4-7.png: PNG image data, 635 x 543, 8-bit gray+alpha, non-interlaced ParkoszIIIF.png:PNG image data, 1920 x 1200, 8-bit/color RGBA, non-interlaced --8<---cut here---end--->8--- Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
[XeTeX] FYI: \includegraphics and *.bb files
Hi! I've created *.bb files as a side effect of experimenting with make4ht when preparing my paper for submitting for publication. I had absolutely no problem with using the images both with XeLaTeX and make4ht. The paper was accepted and several days ago I prepared a final version. To my surprise almost all images was scaled down by XeLaTeX. The test shows the culprit is the presence of *.bb files. There are however some *.bb files which has no such side effect. All *.bb files were created by the same version of the same program, I don't see any essential difference between them. I can live with it, but if somebody is interested I will upload a MWE to the Dropbox. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: Polyglossia: renaming figurname stopped working
On Tue, Mar 26 2019 at 16:12 +09, Akira Kakuto wrote:
>> This happened after the recent upgrade of the Debian packages to texlive
>> 2018.20190227-2. Any suggestions?
>
> Here it seems to work by the following change:
> \begin{document}
> \gappto\captionspolish{\renewcommand{\figurename}{Il.}}
> --->
> \gappto\captionspolish{\renewcommand{\figurename}{Il.}}
> \begin{document}
>
> that is, writing
> \gappto\captionspolish{\renewcommand{\figurename}{Il.}}
> in the preamble.
Thanks, it works.
I cannot locate it now, but somewhere on the Internet there was an
explicit advise to put it after \begin{document}. I followed it and it
worked...
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Polyglossia: renaming figurname stopped working
This happened after the recent upgrade of the Debian packages to texlive
2018.20190227-2. Any suggestions?
Best regards
Janusz
The minimal example:
--8<---cut here---start->8---
\documentclass{article}
\usepackage{fontspec}
\usepackage{polyglossia}
\usepackage{etoolbox}
\setmainlanguage{polish}
\setotherlanguage{english}
\begin{document}
\gappto\captionspolish{\renewcommand{\figurename}{Il.}}
\begin{figure}[!h]
\caption{Test}
\end{figure}
\end{document}
--8<---cut here---end--->8---
The fls file:
--8<---cut here---start->8---
PWD /mnt/MyBookT2/dom/katalog
INPUT /etc/texmf/web2c/texmf.cnf
INPUT /usr/share/texmf/web2c/texmf.cnf
INPUT /usr/share/texlive/texmf-dist/web2c/texmf.cnf
INPUT /var/lib/texmf/web2c/xetex/xelatex.fmt
INPUT figurename.tex
OUTPUT figurename.log
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/article.cls
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/article.cls
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex
INPUT /usr/share/texlive/texmf-dist/fonts/map/fontname/texfonts.map
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/UnicodeData.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/UnicodeData.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/CaseFolding.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/CaseFolding.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/SpecialCasing.txt
INPUT /usr/share/texlive/texmf-dist/tex/generic/unicode-data/SpecialCasing.txt
INPUT /dev/null
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/tuenc.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/tuenc.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/base/tuenc.def
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg
INPUT /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/polyglossia.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/polyglossia.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/makecmds/makecmds.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/makecmds/makecmds.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
INPUT /usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
INPUT /usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex
INPUT /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/gloss-polish.ldf
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/gloss-polish.ldf
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/gloss-polish.ldf
INPUT /usr/share/texlive/texmf-dist/tex/latex/polyglossia/gloss-english.ldf
INPUT
Re: Google Disk
On Sat, Mar 16 2019 at 6:59 +00, Ross Moore wrote: > Hi Janusz, > > On 16/03/2019, at 17:51, "Janusz S. Bień" wrote: > > Sorry for the previous male sent by mistake (the shortcuts in Gnus are > sometimes confusing...) > > On Fri, Mar 15 2019 at 13:34 +01, BPJ wrote: > > Den 2019-03-15 kl. 08:31, skrev Janusz S. Bień: > >> On Fri, Mar 15 2019 at 7:19 +01, BPJ wrote: > >>> I use, despite myself, Google Docs to convert PDF to DOCX, > > For me the quality is similar to Acrobat 9, i.e. completely not > acceptable: spaces between words are often missing. > > This is inherent in the way TeX was written. > But there are ways to tackle the issue. > > You should use the pdfx package and prepare for PDF/A-2b or -2u. > This fixes many of these things that affect conversions, as well as > Accessibility and Archivability. > > It's not fully tagged PDF, but handles many other technical issues. Thanks, I will remember. However for the time being I'm quite happy with make4ht. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Google Disk (was: XeLaTeX to Word/OpenOffice - the state of the art?)
Sorry for the previous male sent by mistake (the shortcuts in Gnus are sometimes confusing...) On Fri, Mar 15 2019 at 13:34 +01, BPJ wrote: > Den 2019-03-15 kl. 08:31, skrev Janusz S. Bień: >> On Fri, Mar 15 2019 at 7:19 +01, BPJ wrote: >>> I use, despite myself, Google Docs to convert PDF to DOCX, For me the quality is similar to Acrobat 9, i.e. completely not acceptable: spaces between words are often missing. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: XeLaTeX to Word/OpenOffice - the state of the art?
On Fri, Mar 15 2019 at 13:34 +01, BPJ wrote:
> Den 2019-03-15 kl. 08:31, skrev Janusz S. Bień:
>> On Fri, Mar 15 2019 at 7:19 +01, BPJ wrote:
>>> I use, despite myself, Google Docs to convert PDF to DOCX,
>>
>> How???
>>
>>> then Pandoc from DOCX to everything else. It works even with weird
>>> magazine layouts.
>>
>> Best regards
>>
>> Janusz
>>
>
> This may be old news to some, but I can’t remember having seen it, so
> I make a post for the record.
>
> I just discovered that you can convert a PDF to Markdown (or any other
> format Pandoc supports) by uploading it to Google Drive, opening it in
> Google Docs and downloading it from there as DOCX, then converting the
> DOCX to Markdown with Pandoc. The result is quite good!
>
> The steps:
>
> 1. Log into in a web browser.
>
> 2. Select the menu [My Drive⏷] → [Upload files…] in the top bar.
>
> More recently there is a “button” [+ New] in the top left
> corner. Click on it and select [File upload] in the menu which
> appears.
>
> 3. At least on my system a file dialog opens. Browse to the PDF file;
> select it; click [Open].
>
> 4. (If this doesn’t work try step 5.)
>
> i. The file appears in the “Quick access” field just below the
> top bar. You may need to refresh a couple of times.
> ii. Right-click the file thumbnail; choose [Open with] → [Google
> Docs].
>
> 5. If step 4 doesn’t work (the PDF file doesn’t appear in the quick
> access field):
>
> i. Start typing the PDF file name in the [Search Drive] box at
> the top.
> ii. Click on the file in the menu which appears.
> iii. The file opens in the Drive PDF viewer.
> iv. At the top there is a menu [Open with Google Docs]. Click on
> it and select Google Docs.
>
> Or look up the file in the file list and follow 4.ii. (Hard when
> there are lots of files in the list!)
>
> 6. You should now find yourself in the Google Docs document view.
>
> 7. In the [File] menu choose [Download as] → [Microsoft Word
> (.docx)].
>
> 8. Save the DOCX file to disk and convert it with Pandoc the same as
> you would any DOCX file, or edit it with Word/LibreOffice/… if you are
> of that persuasion.
>
> Basic formatting — paragraphs, bold, italics — works very well. Some
> more advanced formatting is more or less broken:
>
> - Tables become ordinary text, not very well lined up.
> - Nested lists are flattened.
> - Small caps text disappears entirely! If you have access to the
> original LaTeX file I suggest putting this in your preamble:
>
> \renewcommand\textsc[1]{\textbf{\textit{#1}}}
>
> or if bold italics actually occur in your document this:
>
> \usepackage{textcase}
>
> \renewcommand\textsc[1]{\textbf{\textit{\MakeTextUppercase{#1
>
> Uggly as hell but sequences of uppercase bold italics are unlikely
> to actually occur in a document and are relatively easy to find and
> replace with something better in a “word processor” or in a text
> editor after conversion from DOCX to some sensible format with Pandoc.
>
> If you post-edit in a “WP” you may try (x)color and something like
> \renewcommand\textsc[1]{\textcolor{red}{#1}} instead. That may be hard
> to find _with_ the “WP” but is relatively easy to find _in_ the “WP”
> for a human eye.
>
> You may want to correct these things in the “word processor” but my
> definite preference is to convert the DOCX file to Pandoc’s extended
> Markdown with Pandoc, fix things up and then convert (back) to
> DOCX. You can then also apply your own custom named styles for things
> like color.
>
> http://pandoc.org/MANUAL.html#custom-styles
>
> http://pandoc.org/MANUAL.html#option--reference-doc
>
> It still says “For best results, do not make changes to this file
> other than modifying the styles used by pandoc” but that is just what
> you want to do if you are using custom styles, including adding your
> own! BTW you may want to avoid non-ASCII and non-alphanumeric
> characters in your custom style names so that you don’t need to quote
> your custom-style attribute values!
>
> Speaking of small caps it has its official Pandoc syntax: [small caps
> text]{.smallcaps}, but that is far too verbose by Markdown standards!
> ;-) I usually overload Pandoc’s generally useless strikeout syntax so
> that I can type ~~small caps text~~ with this Pandoc Lua filter:
>
> function Strikeout (elem)
> return pandoc.SmallCaps(elem.content)
> end
>
> I hope this is of use to someone!
>
> /bpj
>
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
solved (was: make4ht problem)
On Tue, Mar 12 2019 at 6:53 +01, Janusz S. Bień wrote: > On Mon, Mar 11 2019 at 13:51 +01, Michal Hoftich wrote: >> Hi Janusz, >> >>> >>> I had to do it already from time to time. I used different methods which >>> were more or less cumbersome. Of course for the conversion I prepare a >>> slightly different text (e.g. no hyphenation). >> >> It is possible to export LaTeX to the ODT format using tex4ht. We >> fixed lot of issues related to Word last year. >> >> Try this command: >> >> make4ht -uxf odt filename.tex Using the recent version from the repository and the configuration file provided to me directly by Michal I converted the XeLaTeX source to the ODT format. I'm impressed by the quality, I will send the file to the editors without any additional hand editing. Thank you Michal! There are some minor rather aesthetic problems which I would like to solve in case the paper will be accepted and I will be asked again to provide the final version in the Word format, but there is no hurry. I can provide all the relevant files to anybody interested via Dropbox. I would like also to thank others who were helpful, especially to Philip Taylor. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: XeLaTeX to Word/OpenOffice - the state of the art?
On Fri, Mar 15 2019 at 7:19 +01, BPJ wrote: > I use, despite myself, Google Docs to convert PDF to DOCX, How??? > then Pandoc from DOCX to everything else. It works even with weird > magazine layouts. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: XeLaTeX to Word/OpenOffice - progress report
On Wed, Mar 13 2019 at 8:34 +01, Michal Hoftich wrote: > Hi Janusz, > >> >> I got no suggestions for make4ht - are the files shared by me on Google >> disk sufficient for diagnosing the problem or should I provide some >> additional information? I promised a minimal example but I would like to >> be sure it is really needed. > > I am working on that. The Biblatex issue was only minor, but there are > bigger issues with images and some other stuff, which results in > non-valid ODT file. I hope to fix that today. Thank you very much! Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
XeLaTeX to Word/OpenOffice - progress report
On Mon, Mar 11 2019 at 12:46 +01, Janusz S. Bień wrote: > Hi! > > I was asked to convert to Word a rather long paper submitted as the > XeLateX PDF output (if accepted, the Word document will be converted to > PDF by the editors...; I understand they work on the assumption that the > reviewers don't know how to comment a PDF file). I have a week for providing the file. Thanks to Phil Taylor I have a result of conversion with the Adobe software which looks reasonable but requires some editing by hand, which I would like to avoid (my knowledge of OpenOffice is rudimentary, so even a simple editing is hard work for me). I got no suggestions for make4ht - are the files shared by me on Google disk sufficient for diagnosing the problem or should I provide some additional information? I promised a minimal example but I would like to be sure it is really needed. I got no suggestions for pandoc. I got no suggestions for latex2html, asked on the latex2html list. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: make4ht problem
On Tue, Mar 12 2019 at 10:38 +01, Michal Hoftich wrote:
> Hi Janusz,
>
>> --8<---cut here---start->8---
>> (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/biblatex.4ht
>> ! Undefined control sequence.
>> ...docsvlist \expandafter {\bbl@loaded
>> }\fi
>> l.228 \fi}{}
>> --8<---cut here---end--->8---
>
> It is hard to say what is going on without a TeX example. This seems
> like an issue with BibLaTeX support, but without trying an actual TeX
> example it is hard to guess what the problem is.
I don't mind sending the source files to anybody interested. I can also
try to prepare a minimal example.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
pandoc problem (was: XeLaTeX to Word/OpenOffice - the state of the art?)
On Mon, Mar 11 2019 at 21:18 +01, Mojca Miklavec wrote: [...] > Pandoc might theoretically support the conversion, but I would not > know how good the results would be. > > Mojca On Mon, Mar 11 2019 at 22:21 -06, Dominik Wujastyk wrote: > I was going to mention Pandoc too. I use it increasingly often, for > various conversions including targetting Word. It's an amazing tool. > Very nice in conjunction with Typora too. --8<---cut here---start->8--- pandoc -f latex -t odt --verbose JSB_Parkosz18word.tex -o JSB_Parkosz18word_pandoc.odt [INFO] Could not load include file 'fontspec.sty' at line 6 column 22 [INFO] Could not load include file 'polyglossia.sty' at line 16 column 25 [INFO] Could not load include file 'etoolbox.sty' at line 17 column 22 [INFO] Could not load include file 'csquotes.sty' at line 20 column 22 [INFO] Could not load include file 'wrapfig.sty' at line 21 column 21 [INFO] Could not load include file 'biblatex.sty' at line 23 column 54 [INFO] Could not load include file 'metalogo.sty' at line 46 column 22 [INFO] Could not load include file 'relsize.sty' at line 55 column 21 [INFO] Could not load include file 'graphicx.sty' at line 59 column 22 [INFO] Could not load include file 'url.sty' at line 61 column 17 [INFO] Could not load include file 'setspace.sty' at line 78 column 37 Error at "source" (line 96, column 8): unexpected JSB \input JSB_Parkosz18-tekst ^ --8<---cut here---end--->8--- This does not seem promising :-( Looks like it just does not handle XeLaTeX. Package: pandoc Version: 2.2.1-3+b2 Versions of packages pandoc suggests: [...] ii texlive-latex-extra2018.20190131-1 ii texlive-latex-recommended 2018.20190131-1 ii texlive-luatex 2018.20190131-1 ii texlive-xetex 2018.20190131-1 -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
XeLaTeX to Word/OpenOffice - the state of the art?
Hi! I was asked to convert to Word a rather long paper submitted as the XeLateX PDF output (if accepted, the Word document will be converted to PDF by the editors...; I understand they work on the assumption that the reviewers don't know how to comment a PDF file). I had to do it already from time to time. I used different methods which were more or less cumbersome. Of course for the conversion I prepare a slightly different text (e.g. no hyphenation). Before embarking on such a job again I would like to make sure there are no new tools that I'm not aware of. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: no more subject prefix for xetex mailing list
On Sun, Mar 03 2019 at 16:05 -07, Karl Berry wrote: > Hi - I've removed the "[XeTeX]" prefix on Subject lines from this > mailing list (xetex)'s messages. It is my hope that this will reduce > the ever-increasing flood of dmarc failures > (https://en.wikipedia.org/wiki/DMARC). Perhaps the Unicode list https://www.unicode.org/mail-arch/unicode-ml/ change addressed the same problem. Before the change in the configuration was applied there was some explanation on the list which unfortunately I don't remember. I don't remeber also when it was done so it makes finding the relevant posting in the archive difficult. >From a user point of view the only visible difference is the from line in the form e.g. Christoph Päper via Unicode . Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Re: [XeTeX] popup windows in XeLaTeX?
On Mon, Feb 26 2018 at 11:11 +0100, zdenek.wag...@gmail.com writes: > Hi, > > I would first try to set the outlines correctly. The PDF specification > says that the outline must either be in AdobeStandardEncoding, which > does not cover east european languages, or each text must be preceded > by BOM. XeTeX inserts BOM automatically. Hopefully luatex (or > hyperref) has an option to do it. It appeared the option is just pdfencoding=unicode: http://tug.org/pipermail/luatex/2018-February/006760.html Thanks to everybody who tried to help. Best regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] popup windows in XeLaTeX?
On Mon, Feb 26 2018 at 6:22 GMT, wvanrooi...@yahoo.com writes: > As far as I know, LuaLaTeX works with UTF-8 (as does XeLaTeX), so that they > should give the same result > > - if the input file is encoded in UTF-8 Yes, it's UTF-8 > - if the same font is used Yes > - if the documentclass is "LuaLaTeX-compatible" I use just the report class. Thanks for your answer, However talking about "the same results" is not appropriate, because the source is unusable with XeLaTeX for reasons described in my previous mail. > On Monday, February 26, 2018 1:02 AM, Janusz S. Bień <jsb...@mimuw.edu.pl> > wrote: [...] > > Hi! > > I use regularly XeLaTeX, but for a specific text I switched to LuaLaTeX > because using the engine, together with ocgx, seemed the simples way to > get footnotes in the form of the popup windows: [...] > Processing the text with XeLaTeX fails on \pdfstartlink, I am aware of a > thread concerning emulating it: > > https://tex.stackexchange.com/questions/86027/how-to-emulate-pdfstartlink-and-pdfendlink-with-xetex > > I would appreciate your advice what is the most easy and/or elegant way > to solve the problem. So my question is whether there is a simple way to make ocgx usable with XeLaTeX and/or whether there is an alternative of using ocgx for creating popup windows. If I decide to stick with Luatex, I will try to solve the problem with the help of the LuaTeX mailing list. Best regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] popup windows in XeLaTeX?
Hi! I use regularly XeLaTeX, but for a specific text I switched to LuaLaTeX because using the engine, together with ocgx, seemed the simples way to get footnotes in the form of the popup windows: https://bitbucket.org/jsbien/parkosz-traktat/downloads/ParkoszLatin.pdf Now I run into some problems with LuaTeX (wrong encoding of Polish letters in the outline); it seems the solution exists but is not a straightforward one. Processing the text with XeLaTeX fails on \pdfstartlink, I am aware of a thread concerning emulating it: https://tex.stackexchange.com/questions/86027/how-to-emulate-pdfstartlink-and-pdfendlink-with-xetex I would appreciate your advice what is the most easy and/or elegant way to solve the problem. Best regards Janusz P.S. I'm sorry for sending it first by mistake to xetex-request. -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] fntsample (was: Does there exist the equivalent of testfont.tex/fonttable.tex for XeTeX?)
On Sun, Jun 14 2015 at 19:07 CEST, k...@freefriends.org writes: which, for a given UNICODE-based font, would print the glyph and the corresponding UNICODE number. Although not TeX, perhaps http://fntsample.sourceforge.net would be useful to you. --karl A student of mine made an interesting extension: https://github.com/ppablo28/fntsample_ucd_comments A sample output: https://bitbucket.org/jsbien/parkosz-font/downloads/fntsampleParkosz.pdf Best regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Future *TeX [was: XeTeX maintenance] (Simon Cozens)
On Mon, Apr 27 2015 at 3:34 CEST, xetex-requ...@tug.org writes: Date: Mon, 27 Apr 2015 10:34:25 +0900 From: Simon Cozens si...@simon-cozens.org To: XeTeX (Unicode-based TeX) discussion. xetex@tug.org Subject: Re: [XeTeX] Future *TeX [was: XeTeX maintenance] Message-ID: 553d9221.2000...@simon-cozens.org Content-Type: text/plain; charset=windows-1252 On 26/04/2015 23:02, Karljurgen Feuerherm wrote: b) assuming a certain level of Xe(La)TeX competence at the ?presenting? level, what recommendations would experts on this list make to ?upping the ante? I.e. progress toward a more insider understanding of the software? OK, I can answer this but I shall add a few other scattered thoughts as well. :-) First I also want to thank Khaled for his fantastic work in keeping xetex maintained, bugs fixed, and users happy. Until recently I presumed that Khaled was a professional software and/or typography person; I didn't realise that xetex was essentially a free time project for him. I was even more amazed by his dedication and professionalism. Me too. Bit by bit, I seem to have picked up how TeX and xetex works, and I wish I could help with the maintainership, but I just don't have the time at present. (And given that I think the future of TeX is spelt SILE I don't think it's appropriate for me to either. ;-) ) How to get to know xetex? I think the first step in moving from a user to understanding the mechanics has to be Victor Eijkhout's TeX By Topic. Either buy a hard copy or download it from https://bitbucket.org/VictorEijkhout/tex-by-topic/src and read it over four or five times. It's by far the best introduction to how the TeX engine works. I support this. The strange thing is that despite such a large community of users nobody created a TeX debugger. The only one unfinished attempt seems to that presented in 1995 (!) in Bachotek: Lutz Birkhan: The TeX debugger Proceedings of the Eight European TEX Conference, September 26-30, 1994, Gdańsk, Poland, pp 91-95. The interface seemed quite reasonable and the author was willing to make the code available, but looks like nobody was interested. My tiny contribution is also unfinished: https://bitbucket.org/jsbien/emacs-tex-output-browser Best regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Fine tune selecting alternate glyphs
On Tue, Feb 09 2010 at 6:24 CET, hospes.pri...@verizon.net writes: [...] XeTeX comes with that nifty utility that allows one to identify the OT or AAT features that exist in a font. It would be very helpful if there were a similar utility that would identify which characters have stylistic alternates. Running such a utility on a font would produce a list like this: a - 5 variants, b - 1 variant, e - 4 variants, g - 6 variants, etc. One could then construct a test document to see which alternates are accessed with which numbers. This is an important issue because some font makers don't provide exact information about what characters have alternate glyphs, even if they tell you that the font does contain stylistic alternates. (I guess they assume everyone uses an application like InDesign or Quark that comes with a palette to show the alternates.) Without this information XeTeX users can't access the variants since they have to be called numerically. Anybody want to write something like this? (I would do it but I don't have the programming skills.). I would also like very such a tool. Do I understand correctly there is still none? Best regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] howto xelatex and auctex
On Mon, 17 Sep 2012 Jacobo Myerston jmyers...@gmail.com wrote: I'm working on highly annotated documents using xelatex. I have been working with texshop, but I want to use emacs (actually aquamacs) as an editor because of the capabilities of the auctex package for emacs to fold chunks of code, like footnotes, etc. For my surprise, I found that emacs 24 still does not support xelatex out the box. It has a xetex engine, but not xelatex. I find that different people have some hacks to get it work, but I cannot find any documentation (step by step) how to configure emacs to works properly with xelatex. Does anybody knows how to get xelatex to work properly with emacs without having to use the prompt every time you want to compile? This ;;set xetex mode in tex/latex (add-hook 'LaTeX-mode-hook (lambda() (add-to-list 'TeX-command-list '(XeLaTeX %`xelatex%(mode)%' %t TeX-run-TeX nil t)) (setq TeX-command-default XeLaTeX) (setq TeX-save-query nil) (setq TeX-show-compilation t) )) comes, if I remember correctly, from the page http://hephaistos-text.org/open-source-classics/82-emacs-auctex-and-xelatex.html which is no longer available. Regards Janusz -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Dinosaurs
On Mon, 12 Sep 2011 Barry MacKichan barry.mackic...@mackichan.com wrote: [...] All input was on paper tape. The equivalent of the delete key, as I recall, was opaque tape that you could stick on the paper tape. Or punching all the holes in the row. My first computer was GIER http://www.mimuw.edu.pl/wydzial/zdjecia/zosk/ with 1 K RAM of 42-bit words. Regards JSB -- , Prof. dr hab. Janusz S. Bien - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX in lshort
On Tue, 28 Sep 2010 Peter Dyballa peter_dyba...@web.de wrote: Am 28.09.2010 um 16:20 schrieb Tobias Schoel: Can we now come back to the beginning problem: Which way of creating unicode-encoded .tex-documents to propose in lshort? Using GNU Emacs 23.x √ the Unicode Emacs (and any of its variants) √ with its AUCTeX extension. I support this. Regards Janusz -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Ligatures and searching in PDFs
On Mon, 10 May 2010 David J. Perry hospes.pri...@verizon.net wrote: The proper solution would be to use /ActualText feature of the PDF specification. I am very interested in this issue of searching PDFs. A google search for PDF Actual Text turned up nothing. I then downloaded the actual PDF spec from the Adobe web site and found the reference, and got the idea of what it's about. But how do people like me who use commonly available tools such as XeLaTeX to make PDFs implement this? Could you say a little more about this feature or provide pointers to some information? Unfortunately this is just a wishlist. The access to the feature in XeLaTeX and other open source tools is yet to be designed and implemented. Best regards Janusz -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Ligatures and searching in PDFs
On Tue, 11 May 2010 Khaled Hosny khaledho...@eglug.org wrote: [...] IIRC, there are already latex packages that adds higher level support for ActualText tags (low level support is already in the engines). You are right: http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/accsupp.pdf I was not aware of it. Best regards Janusz -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/ -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
