Tobias Schoel wrote:
So would it be wise to make for example u2009 (narrow space) and u202f
(narrow no break space) active and map it to {\,} or {\nolinebreak\,}
respectively?
IMVHO, this should be as unnecessary (and insane) as
making u00E9 (é) active and mapping it to {\'e}. Surely
if
On Thu, 3 Mar 2011, Philip Taylor (Webmaster, Ret'd) wrote:
if XeTeX is predicated on the use of Unicode, it should
understand the semantics of Unicode code points such
as u2009 and u202F and just do the right thing without
having to hack things through the use of active characters.
There are
msk...@ansuz.sooke.bc.ca wrote:
On Thu, 3 Mar 2011, Philip Taylor (Webmaster, Ret'd) wrote:
if XeTeX is predicated on the use of Unicode, it should
understand the semantics of Unicode code points such
as u2009 and u202F and just do the right thing without
having to hack things through the use
Peter Davis wrote:
However, running one test of 34,500 pages took 10 hours(!) to compile
with XeLaTeX. This was on a 3GHz/4Gb Windows 7 Pro machine, using the
XeTeX from MiKTeX 2.9.
I expected this job to complete in a matter of minutes, but it basically
took 100 times longer than I
Peter Davis wrote:
I expected this job to complete in a matter of minutes, but it basically
took 100 times longer than I anticipated. The job uses perhaps a dozen
PDFs via \includegraphics, but it uses the sames ones over and over
again. It also uses \textpos to position blocks of text
2011/3/3 Philip Taylor (Webmaster, Ret'd) p.tay...@rhul.ac.uk:
No, but as you have yourself suggested two possible causes,
Please stop jumping to conclusions and switching to other mailing lists.
Best
Martin
--
Subscriptions, Archive, and
Martin Schröder wrote:
2011/3/3 Philip Taylor (Webmaster, Ret'd)p.tay...@rhul.ac.uk:
No, but as you have yourself suggested two possible causes,
Please stop jumping to conclusions and switching to other mailing lists.
Please explain what leads you to believe I have jumped to
any
On Thu, 3 Mar 2011, enrico.grego...@univr.it wrote:
\newunicodechar{2009}{\,\hspace{0pt}}
\newunicodechar{202f}{\,}
Of course it works.
The main purpose of the package is indeed to use the real char. Actually
those who don't know how to input it will never use the packages to
I guess this isn't really the place for this query, but perhaps someone has
had a similar problem.
I'm using XeTeX and TeXWorks for academic work, like many of us. I
cut-n-past bibliographical information from sites like copac.ac.uk and
worldcat.org, into JabRef for use in my documents. What
* Dominik Wujastyk (wujas...@gmail.com) wrote:
| bibliographical information from sites like copac.ac.uk and worldcat.org,
into
| JabRef for use in my documents. What I'm finding, though, is that
several of
| these big online bibliographical databases have their records in
Might this be of use, Dominik ?
http://download.oracle.com/javase/6/docs/api/java/text/Normalizer.html
** Phil.
Dominik Wujastyk wrote:
What I'd like, ideally, is a little filter to run on my bib files
periodically to clean up any char+non-spacing-accent glyphs.
Am 03.03.2011 um 18:34 schrieb Dominik Wujastyk:
What I'd like, ideally, is a little filter to run on my bib files
periodically to clean up any char+non-spacing-accent glyphs.
Maybe UnicodeChecker (http://earthlingsoft.net) could help – via its
services, so it's for interactive use.
--
Am 03.03.2011 14:38, schrieb msk...@ansuz.sooke.bc.ca:
On Thu, 3 Mar 2011, Philip Taylor (Webmaster, Ret'd) wrote:
if XeTeX is predicated on the use of Unicode, it should
understand the semantics of Unicode code points such
as u2009 and u202F and just do the right thing without
having to hack
Hi,
I'm testing some code I wrote to generate .tex files from XML files. These
.tex files are then processed via XeLaTeX to produce PDF. The code seems to
be working, in that I get a valid .tex file, which then compiles into a
valid PDF.
However, running one test of 34,500 pages took 10
On Thu, Mar 3, 2011 at 10:13 AM, Peter Davis p...@pfdstudio.com wrote:
Hi,
I'm testing some code I wrote to generate .tex files from XML files. These
.tex files are then processed via XeLaTeX to produce PDF. The code seems to
be working, in that I get a valid .tex file, which then compiles
Hi Phil,
Sent from my iPad
On 04/03/2011, at 3:12 AM, Philip Taylor (Webmaster, Ret'd)
p.tay...@rhul.ac.uk wrote:
Martin Schröder wrote:
2011/3/3 Philip Taylor (Webmaster, Ret'd)p.tay...@rhul.ac.uk:
No, but as you have yourself suggested two possible causes,
Please stop jumping to
Well, maybe : but why did he cite my message and
not Peter's in that case ?!
** Phil.
Ross Moore wrote:
Martin Schröder wrote:
2011/3/3 Philip Taylor (Webmaster, Ret'd)p.tay...@rhul.ac.uk:
No, but as you have yourself suggested two possible causes,
Please stop jumping to conclusions
Hi Phil,
Sent from my iPad
On 04/03/2011, at 6:56 AM, Philip Taylor (Webmaster, Ret'd)
p.tay...@rhul.ac.uk wrote:
Well, maybe : but why did he cite my message and
not Peter's in that case ?!
The original message was sent to texhax (without delay) and XeTeX (held for
moderation), and you
Looks good. But wot is a Mac?
On 3 March 2011 19:07, Peter Dyballa peter_dyba...@web.de wrote:
Am 03.03.2011 um 18:34 schrieb Dominik Wujastyk:
What I'd like, ideally, is a little filter to run on my bib files
periodically to clean up any char+non-spacing-accent glyphs.
Maybe
WOW! I had no idea it was in there. I'll to some tests and report back.
Dominik
On 3 March 2011 20:30, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Mar 03, 2011 at 06:34:48PM +0100, Dominik Wujastyk wrote:
I guess this isn't really the place for this query, but perhaps someone
has
Very preliminary tests, using this:
@book{Vāgbhaṭa:1939,
author = {Vāgbhaṭa, and Gode, P. K. (Parshuram Krishna) and Kuṇṭe,
Aṇṇā Moreśvara. and Navare, Kr̥ṣṇaśāstrī. and Parāḍakara,
Hariśāstrī Sadāśiva.},
title= {Aṣṭāṅgahr̥dayam},
edition = {6th ed.},
address =
Dominik Wujastyk wrote:
Looks good. But wot is a Mac?
Oh come on, Dominik, you're not that young or naïve :
you know perfectly well it is what certain gentlemen
of unusual persuasions would put on before entering
a particular genre of bookshop in London's Soho ...
** Phil.
Am 03.03.2011 um 21:21 schrieb Dominik Wujastyk:
But wot is a Mac?
A big and ugly iPad which is good for something.
--
Greetings
Pete
Only useless documentation transcends the first two laws.
– Arnold's Third Law of Documentation
On 3 Mar 2011, at 20:32, Dominik Wujastyk wrote:
Very preliminary tests, using this:
@book{Vāgbhaṭa:1939,
author = {Vāgbhaṭa, and Gode, P. K. (Parshuram Krishna) and Kuṇṭe,
Aṇṇā Moreśvara. and Navare, Kr̥ṣṇaśāstrī. and Parāḍakara,
Hariśāstrī Sadāśiva.},
title=
Am 03.03.2011 um 21:32 schrieb Dominik Wujastyk:
show improvement, but the r-undercircle character (as in
Kr̥ṣṇaśāstrī)
results in a blank space.
This character does not exist in composed form. You need to form it
yourself. Best, using a font with COMBINING RING BELOW at U+0325.
25 matches
Mail list logo