On Fri, 19 Mar 2010 Peter Baker wrote:
[...]
> Emacs hasn't been Unicode-aware for a whole long time;
http://www.cl.cam.ac.uk/~mgk25/unicode.html
Emacs has quite good basic UTF-8 support starting from version 21.3
Emacs 21.3 was released on March 24, 2003.
Best regards
Janusz
--
On Mon, 10 May 2010 Paul Foley wrote:
> 1. (*) text/plain ( ) text/html
>
> Try the following:
>
> \documentclass{article}
> \usepackage{xltxtra}
> \setmainfont[Mapping=tex-text,Numbers=OldStyle,Ligatures={Required,Common,Rare}]{Junicode}
>
> \begin{document}
> Fifty afflict
On Mon, 10 May 2010 "David J. Perry" 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
>
On Tue, 11 May 2010 Khaled Hosny 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 awar
On Tue, 28 Sep 2010 Peter Dyballa 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) √
On Tue, 5 Oct 2010 Peter Dyballa wrote:
> Am 05.10.2010 um 12:46 schrieb Dominik Wujastyk:
>
>> This is completely wrong, and anachronistic. SGML was born long
>> after TeX
>> and LaTeX.
>
> You probably mean that ISO standard on SGML from 1986 (8879). There is
> none for any TeX dialect...
>
On Mon, 12 Sep 2011 Barry MacKichan 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/zdjeci
On Mon, 17 Sep 2012 Jacobo Myerston 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 footnot
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
> stylis
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
> To: "XeTeX (Unicode-based TeX) discussion."
> Subject: Re: [XeTeX] Future *TeX [was: XeTeX maintenance]
> Message-ID: <553d9221.2000...@simon-cozens.org>
> Content-Type:
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
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 problem
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, Febru
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 BO
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
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 t
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 exp
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
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
>>
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
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
>>
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.goo
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
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
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
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
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}
\usepacka
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.}}
> --
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 surpr
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 p
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
Th
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
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{fontsp
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
--
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/s
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
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
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 th
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
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 t
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? W
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)
>
>
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,
>
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
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).
>
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
>
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
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 prov
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
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ń wrot
50 matches
Mail list logo
