As subject. xdv is the eXtended DVi format used by XeTeX.
I did a search on the mailing list archive and nothing came up.
http://www.mail-archive.com/search?l=dev-luatex%40ntg.nl&q=xdv
Jonathan
___
dev-luatex mailing list
dev-luatex@ntg.nl
Mojca Miklavec wrote:
On Thu, Jan 1, 2009 at 11:09 PM, Jonathan Fine wrote:
What I want is for LuaTeX and XeTeX to have a shared 'extended dvi format'
which is suitable for print, for generating PDF and possibly other purposes.
Just curious: how do you print xdv (what's wron
> As subject. xdv is the eXtended DVi format used by XeTeX.
Actually, it can. LuaTeX produces DVI, which is perfectly palatable
to XeTeX's xdv2pdf and xdvipdfmx. What features of xdv are you missing
in LuaTeX's output?
Arthur
__
On Thu, Jan 1, 2009 at 11:09 PM, Jonathan Fine wrote:
>
> What I want is for LuaTeX and XeTeX to have a shared 'extended dvi format'
> which is suitable for print, for generating PDF and possibly other purposes.
Just curious: how do you print xdv (what's wrong with print
n why a 'special'
> that says 'do (b)' should not be written to the xdv or whatever output
> file.
Maybe it's time that we turn the question the other way round and ask
you for reasons to *do* so. What, could you please tell us, is so great
about *not* generat
Hi all,
Arthur Reutenauer wrote:
As subject. xdv is the eXtended DVi format used by XeTeX.
Actually, it can. LuaTeX produces DVI, which is perfectly palatable
to XeTeX's xdv2pdf and xdvipdfmx. What features of xdv are you missing
in LuaTeX's output?
As Barry said in anoth
me restate (better this time, I hope).
Can, in all important cases, the transformation
Source to PDF via LuaTeX
proceed via
Source to xdv (say via a modified LuaTeX)
and then
xdv to PDF (say by xdvipdfm).
From what you've said, it seems to me that xdv contains some but not all of
th
Jonathan Fine wrote:
As subject. xdv is the eXtended DVi format used by XeTeX.
No, it cannot. Perhaps it should, but that needs a volunteer.
Best wishes,
Taco
___
dev-luatex mailing list
dev-luatex@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev
on extended DVI format, not for LuaTeX to produce xdv, right? This
is quite different since, as I said above, LuaTeX has some features that
XeTeX's xdv can't account for.
I think you've got the gist of what I want. Sharing of code and ideas.
However, your statement seems to con
Arthur Reutenauer wrote:
As subject. xdv is the eXtended DVi format used by XeTeX.
Actually, it can. LuaTeX produces DVI, which is perfectly palatable
to XeTeX's xdv2pdf and xdvipdfmx. What features of xdv are you missing
in LuaTeX's output?
Knuth and MacKay were the first to
here.
Please could I be told, what are the main benefits of directly producing
PDF?
BTW, Jonathan Kew said recently (on c.t.t) that XeTeX can use two
processors on a multicore machine precisely because typesetting and PDF
generation are decoupled, via xdv
pdfTeX about included
PDFs.
> BTW, Jonathan Kew said recently (on c.t.t) that XeTeX can use two processors
> on a multicore machine precisely because typesetting and PDF generation are
> decoupled, via xdv.
I doubt the speed gained from that is high for most documents.
But as I said: Sh
plates section.
>
> In both cases we have to open the image file and, as you say, reason about
> it. Based on this reasoning we come to a conclusion (such as a scale
> factor) and both 9a) typeset the text and (b) process the image accordingly.
>
> LuaTeX does (a) and (b) at the
ill
possible.
> I'm looking for a what might be called a Unicode savvy Device Independent
> binary format. And I'm looking for XeTeX and LuTeX to share code and
> ideas, when possible.
Hence, what you're aiming at is for LuaTeX and XeTeX to produce some
common extend
same result. But in most cases, it
should still work, though. Again, it all depends on what kind of
information you want to put it your output file, so you should be more
specific.
> From what you've said, it seems to me that xdv contains some but not all of
> the features that LuaT
you would have to
include in the xdv file a map from glyph indexes to Unicode strings,
perhaps using specials.
___
dev-luatex mailing list
dev-luatex@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-luatex
On Fri, Mar 27, 2009 at 07:14:01PM +0900, Jin-Hwan Cho wrote:
> Could you show me any DVI (or XDV) file which cause your problem?
I couldn't run your test, I' getting:
** WARNING ** Could not open config file "dvipdfmx.cfg".
mytest.dvi -> mytest.pdf
** WARNING
David Kastrup writes:
> So I don't think that the DVI format does not make for a sensible
> starting point for embedding such information.
Read what I mean, not what I write.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
___
dev-luatex mailing lis
Jonathan Fine skribis:
> Well, it's not MY code, but I'm sure you're welcome to use it:
>http://scripts.sil.org/svn-public/xetex/TRUNK/
>http://scripts.sil.org/svn-public/xdvipdfmx/TRUNK/
>
> XeTeX is distributed under the X11 free software license.
xdvipdfmx is GPL, I believe.
_
dingly.
LuaTeX does (a) and (b) at the same time. I see no reason why a
'special' that says 'do (b)' should not be written to the xdv or
whatever output file.
[Discussion of performance snipped]
But as I said: Show us your code.
Well, it's not MY code, but I'
2009/1/1 Jonathan Fine :
> What I want is for LuaTeX and XeTeX to have a shared 'extended dvi format'
> which is suitable for print, for generating PDF and possibly other purposes.
Thus loosing the benefits of directly producing PDF. I don't see many
benefits here.
But of course patches implementi
Jonathan Fine wrote:
Please could I be told, what are the main benefits of directly producing
PDF?
Convenience since all is packages in one file; also, it's in the spirit
of good old tex to adapt to developments (like pdf). Nowhere is demanded
that dvi is to be the output (in a similar fashi
Jonathan Fine writes:
> Yannis Haralambous wrote:
>
>> the original DVI format already supports 4-byte character, what more
>> Unicode-savviness do you need? Of course one should decide whether
>> DVI should contain glyph indexes or Unicode codepoints.
>
> I'd like bidirectional information to be
Taco Hoekwater wrote:
[discussion of plans snipped]
PDF is very strong in the print field. However, the web page is also an
important medium, and as I said in my response to Mojca, I'd like to be
able to view and interact with typeset material on a more-or-less
ordinary web page.
I'd also
Arthur Reutenauer writes:
> Maybe it's time that we turn the question the other way round and ask
> you for reasons to *do* so.
Hi Arthur,
as far as I remember, Jonathan explained clearly at the very beginning
of the discussion why he is interested in an intermediate format.
> What, could
2009 at 07:14:01PM +0900, Jin-Hwan Cho wrote:
Could you show me any DVI (or XDV) file which cause your problem?
I couldn't run your test, I' getting:
** WARNING ** Could not open config file "dvipdfmx.cfg".
mytest.dvi -> mytest.pdf
** WARNING ** Failed to load AGL file &
Jonathan Fine skribis:
> I'm looking for a what might be called a Unicode savvy Device Independent
> binary format. And I'm looking for XeTeX and LuTeX to share code and
> ideas, when possible.
Glyph indexes plus a ToUnicode map. That's how Unicode-savviness is
done in a PDF: each glyph index
Yannis Haralambous wrote:
the original DVI format already supports 4-byte character, what more
Unicode-savviness do you need? Of course one should decide whether DVI
should contain glyph indexes or Unicode codepoints.
I'd like bidirectional information to be available.
Unless you mean by Uni
Yannis Haralambous wrote:
1) I put tags in the DVI file which allow me to place marginal material
at (exactly) the same height, during post-processing. In DVI it is easy
to place a PUSH, make a skip, typeset the material and then POP back to
the previous position so that the rest of the page r
Yannis Haralambous wrote:
Talking about DVI and PDF, I am the first one to be concerned about the
programmed extinction of DVI because I have many jobs based on DVI
post-processing (for example for marginal material, headers, and even
for parallel texts between two pages). The advantage with DV
the original DVI format already supports 4-byte character, what more Unicode-savviness do you need? Of course one should decide whether DVI should contain glyph indexes or Unicode codepoints.Unless you mean by Unicode-savviness that one should have both glyph indexes and Unicode codepoints (I think
Jonathan Fine wrote:
What I want is for LuaTeX and XeTeX to have a shared 'extended dvi
format' which is suitable for print, for generating PDF and possibly
other purposes.
And of course I'd like this format to be of at least satisfactory
technical quality.
Since luatex is mostly pdftex th
Jonathan Fine wrote:
Taco Hoekwater wrote:
[discussion of plans snipped]
PDF is very strong in the print field. However, the web page is also an
important medium, and as I said in my response to Mojca, I'd like to be
pdf is also quite strong in the preview on the web field; it packages
al
nformation was ignored only in the
CIDFontType0C format.
And, Adobe Reader 9 does not look good.
Best regards, ChoF.
On Mar 28, 2009, at 6:03 AM, Khaled Hosny wrote:
On Fri, Mar 27, 2009 at 07:14:01PM +0900, Jin-Hwan Cho wrote:
Could you show me any DVI (or XDV) file which cause your problem?
Le 2 janv. 09 à 21:49, Hans Hagen a écrit :i'm not sure if you refer to the same kind of positional info, but pdftex (and therefore luatex) hasn pdfsavepos cum suis in both pdf and dvi mode so you can store positions (lazy, i.e. write them to file in the backend) and then use them in a second pass
Talking about DVI and PDF, I am the first one to be concerned about the programmed extinction of DVI because I have many jobs based on DVI post-processing (for example for marginal material, headers, and even for parallel texts between two pages). The advantage with DVI is that you can very easily
36 matches
Mail list logo
