Hi,
This message is prompted by a bug report for t-vim
(https://github.com/adityam/filter/issues/43), but the issue is more general.
Whenever, `cssfile` in `\setupexport` points to a file now in $PWD, the
reference to the file in the exported CSS is incorrect:
Consider the following directory
of that). I thought that
\startelement[mycommand][name=whatever]
should work (there are some such examples in the texmf tree), but it does
not.
epub-mkiv.pdf states that I need `\setupexport[properties=yes]`, but that
doesn't work either:
There is a bug in back-exp.lua:
--- /tmp/back-exp.lua
][name=whatever]
should work (there are some such examples in the texmf tree), but it does
not.
epub-mkiv.pdf states that I need `\setupexport[properties=yes]`, but that
doesn't work either:
```
\setupbackend[export=xml]
\setupexport [properties=my]
\setelementbackendtag[mycommand
iple output for
> publishing
> ane educational purposes. And it looks pretty good too.
>
Thank you very much i will do. You are refering to Thomas Schmitz?
\setupbackend[
export=yes,
xhtml=yes
]
\setupexport[
title={linenumber placement missmatch example in export},
subtitle={},
au
On 1/10/2020 10:59, Rik Kabel wrote:
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
\starttext
!
\stoptext
and in the resulting export styles directory, I get:
g:\yoiks-export\styles>grep "namespace\|weight.*ital
ly assigns italic to font-weight when of course it is
a font-style as far as css is concerned. This can be seen in file
export-example.css in the distribution.
can you make a mwe ...
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
font-style : inherit ;
font-variant : inherit ;
font-weight : inherit ;
font-family : inherit ;
color : inherit ;
text-decoration : underline ;
}
xxx.tex:
\setupbackend[export=yes]
\setupexport[cssfile=xxx.css]
\definehigh
to get two
(or all to get three, or...). There are similar problems with tabulate
and xtables, but only TABLE is shown here.
\setupstructure[state=start,
method=auto]
\setuptagging [state=start]
\setupbackend [export=yes]
\setupexport
The following example fails with recent betas, but not with TL18:
\setupinteraction [state=start]
\setuptagging [state=start]
\setupbackend [export=yes,xhtml=yes]
\setupexport [title={Title}]
\setupstructure [state=start]
\starttext
\startchapter[title
dd attributes
>> as you say), but I feel bad about posting to the list for them. Is there
>> any documentation for these features at all? I couldn't find any
>> reference to the \startelement command when I looked, but perhaps I'm
>> looking in the wrong place.
>
>
. Is there
any documentation for these features at all? I couldn't find any
reference to the \startelement command when I looked, but perhaps I'm
looking in the wrong place.
\setupbackend[export=yes]
\setupexport[properties=yes]
\starttext
\startelement[test][this=that]whatever\stopelement
Hi again,
I'm trying to define a cover image for my ePub using the documented „firstpage“
setting of \setupexport.
While it works in my minimal example below, it fails in my project structure; I
tried to move \setupexport into project, product and component to no avail.
%
\setupbackend[export
of \setupexport.
While it works in my minimal example below, it fails in my project structure;
I tried to move \setupexport into project, product and component to no avail.
%
\setupbackend[export=yes]
\setupinteraction[
state=start,
color=,contrastcolor=,
title={ePub
Dear gang,
Here are two export bugs, full test suite attached:
==sh_ahmad-qajar-xml-test-highlight.tex===
\setupexport[cssfile=sh_ahmad-qajar.css]
\setupbackend[export=yes]
\definehighlight[emphasis][style=\em]
\definehighlight[important][style=bold]
\starttext
to
\start-stophead. A simple
\definestartstop[heading][style=]
does the trick, and may be worth adding to the distribution.
Best wishes
Idris
=
\setupexport[cssfile=itemize.css]
\setupbackend[export=yes]
\setupitemize[each][headstyle=bold]
\definestartstop[heading][style=]
\starttext
'
I’m using in the env file:
\setupbackend
[export=yes]
\setupexport
[title={Chess and the Art of Enterprise Architecture},
author={Gerben Wierda},
firstpage={9789081984058-CoverFront.jpeg},
]
So, what seems to be ignored is
\setupexport
[title={Chess and the Art of Enterprise
Dear gang,
In the attached, we export hemistiches:
===
\setupexport[cssfile=sh_ahmad-qajar.css]
\setupbackend[export=yes]
\usemodule[hemistich]
\setuphemistich
[width=local,
distance=1\emwidth,
separator=]
\setuphemistich
[leftcolor=,
separatorcolor
Am 18.03.2015 um 15:04 schrieb Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu:
Dear gang,
In the attached, we export hemistiches:
===
\setupexport[cssfile=sh_ahmad-qajar.css]
\setupbackend[export=yes]
\usemodule[hemistich]
\setuphemistich
[width=local
isha...@colostate.edu:
Dear gang,
In the attached, we export hemistiches:
===
\setupexport[cssfile=sh_ahmad-qajar.css]
\setupbackend[export=yes]
\usemodule[hemistich]
\setuphemistich
[width=local,
distance=1\emwidth,
separator=]
\setuphemistich
[leftcolor
On Wed, 18 Mar 2015 11:51:13 -0600, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
Am 18.03.2015 um 15:04 schrieb Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu:
Dear gang,
In the attached, we export hemistiches:
===
\setupexport[cssfile=sh_ahmad-qajar.css
Ok, I've made some progress:
On Sun, 15 Mar 2015 17:01:16 -0600, Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu wrote:
export-highlight.tex==
\setupbackend
[export=yes,css=highlight.css]
\setupexport[cssfile=highlight.css]
\setupbackend[export=yes
\input darwin
9
10 \setupexport
11 [hyphen=yes,
12width=60em]
13
14 \stopmode
15
16 \starttext
17
18 \startquotation
19 \input darwin
20 \stopquotation
21
22 \stoptext
Please advise.
Best wishes
Idris
It's one of those weird things
Hi Alan,
On Wed, 14 Jan 2015 10:55:50 -0700, Alan BRASLAU alan.bras...@cea.fr
wrote:
\enablemode[export]
\startmode[export]
\setupbackend
[export=yes,
xhtml=yes,
css=export-example.css]
\setupexport
[hyphen=yes,
width=60em]
\stopmode
\starttext
converted to Word is another problem that is to be addressed to the
MS-Word community.
Hans showed us at the last ConTeXt conference:
MWE:
\enablemode[export]
\startmode[export]
\setupbackend
[export=yes,
xhtml=yes,
css=export-example.css]
\setupexport
[hyphen=yes
it with any specification file, but only
with a plain ConTeXt file like
\setupbackend[
export=export.xml,xhtml=yes,
]
\setupexport[
firstpage={koe.png},
]
\settaggedmetadata[
author={Hraban},
]
\starttext
\startchapter[title={Chapter One}]
\startsection[title={Section
=yes,
]
\setupexport[
firstpage={koe.png},
]
\settaggedmetadata[
author={Hraban},
]
\starttext
\startchapter[title={Chapter One}]
\startsection[title={Section One}]
\input tufte
\stopsection
\startsection[title={Section Two}]
\input knuth
\externalfigure[koe][width
about ePub says, it should be possible to define metadata in
\setupexport like this:
\setupexport[
firstpage={koe.pdf},
title={My Fine Title},
]
But that is completely ignored - it does neither show up in the export, nor in
a produced ePub.
If I include an image
Hi again.
I understand you don’t want to export some arbitrary (X)HTML. That’s fine, I
can make my own XSLT.
And I’m glad that \setupexport doesn’t kill hyphenation any more.
But there are serious errors in export, that have nothing to do with „there’s
no usable standard“.
[1] root node
Hi,
I tried to compile one of my projects to a EPUB by adding
\setupbackend[export=yes,xhtml=yes]
\setupexport
[title={A nice book},
author={John Doe},
firstpage={huhn.jpg},
]
to the main-file. After that I began the compiling by
C:\Users\diretorymtxrun --script epub --make
offer the flexibility of custom XML documents without
affecting the default behaviour.
* Generates XHTML headers (including !DOCTYPE and html...)
not needed as we're 'standalone'
Having the ability to produce the !DOCTYPE... and htmnl elements
could be as simple as:
\setupexport
offer the flexibility of custom XML documents without affecting
the default behaviour.
* Generates XHTML headers (including !DOCTYPE and html...)
not needed as we're 'standalone'
Having the ability to produce the !DOCTYPE... and htmnl elements could
be as simple as:
\setupexport[
standalone
]
\setupexport[
title={A nice book},
author={John Doe},
firstpage={cover.jpg},
]
\starttext
\startitemize
\item First
\item Second
\item Third
\stopitemize
\stoptext
I then ran mtxrun:
mtxrun --script epub --make t.specification
This produced a document
Please try the following example:
-- start code --
\setupbackend[export=yes,xhtml=test_00.xhtml]
\mainlanguage[de]
\language[de]
\setupexport
[title={A nice book},
author={Andy Tom},
firstpage={huhn.jpg},
]
\starttext
Hello world!
\stoptext
-- end code --
The firstpage
On 9-6-2012 14:58, Andy Thomas wrote:
On Jun 9, 2012, at 1:31 AM, Hans Hagen wrote:
On 8-6-2012 23:28, Andy Thomas wrote:
Thank you for the suggestions. I will try to implement it, but might need until
Sunday.
- I've added some keys to \setupexport:
author
title
subtitle
On Jun 9, 2012, at 1:31 AM, Hans Hagen wrote:
On 8-6-2012 23:28, Andy Thomas wrote:
Thank you for the suggestions. I will try to implement it, but might need
until Sunday.
- I've added some keys to \setupexport:
author
title
subtitle
firstpage (also new key in mult)
lastpage
={}]
Backends other than epub can safely ignore the directive.
better is
\setupexport
(actually, we do have \setupdocument which makes een more sense:
(1) take from setupdocument
(2) if empty take from setupexport
(3) otherwise take from setupinteraction
In one of your earlier threads
On 8-6-2012 23:28, Andy Thomas wrote:
Thank you for the suggestions. I will try to implement it, but might need until
Sunday.
- I've added some keys to \setupexport:
author
title
subtitle
firstpage (also new key in mult)
lastpage (aso new key in mult)
- The title, subtitle
On Sat, 9 Jun 2012, Hans Hagen wrote:
On 8-6-2012 23:28, Andy Thomas wrote:
Thank you for the suggestions. I will try to implement it, but might need
until Sunday.
- I've added some keys to \setupexport:
author
title
subtitle
firstpage (also new key in mult)
lastpage (aso new key
Ramm}]
\setupexport[bodyfont=12pt,hyphen=yes]
\starttext
\startchapter[title=Test]
\input tufte
\stopchapter
\stoptext
Hm, the xhtml file doesn’t look like HTML at all, and even styling the
existing tags in CSS doesn’t affect the output.
If I change sectiontitle to xhtml:h2, it’s reckognized
...
empty file
* ./test
?
Any ideas on how to fix this?
Also, I looked at back-exp.mkiv and it appears that xhtml export is
possible. If so, what is the command to enable it. (I am guessing
\setupexport[export=yes, xhtml=yes] but cannot test it due to the above
error).
Aditya
40 matches
Mail list logo
