Re: [NTG-context] What happened to the ePub script?

2015-01-20 Thread Hans Hagen

On 1/20/2015 10:16 AM, Henning Hraban Ramm wrote:

Am 2015-01-19 um 15:48 schrieb Hans Hagen :


On 1/17/2015 1:52 PM, Henning Hraban Ramm wrote:

* How can I set the current \date in a metadata variable?
(I know it’s also in the date tag of , but I know how to format \date 
…)

This doesn’t work (i.e. I get „\date“ in XML/XHTML):

\settaggedmetadata[
version={\date}
]


\the\normalyear-\the\normalmonth-\the\normalday


Thanks, but that’s not the same. Not only because I get „2015-1-20“ and not 
„2015-01-20“.

Is there a way to get „everything“ expanded within \settaggedmetadata ?


no, because \hbox{foo\smallcaps bar\kern10pt gnu} and such have no real 
string representation



* Can I influence the directory/file names of the export from within the source?
E.g. if I compile „minimal.tex“, I get minimal-export and minimal-epub
The —result switch doesn’t change anything.


hm, honoring --result is doable but in general i'd like to keep the export 
quite basic and predictable (the less options the better)


Ok, that means we have no influence on files names at all?


it would only be the directory and maybe the main files but not every 
specific file (it would demand an extra setup and lots of explanations 
in the manual) but maybe at soem point the mtx-epub script can do some 
magic ... it's already tricky to keep up cq. satisfy basic epub 
standards and it's really no fun to do that kind of stuff ... i have no 
real need for it so i cannot spend ages on it ... (in fact i only redid 
it because i wanted to play with the svg math and then noticed some 
possible improvements in the rest



* BTW: Can I set —result from within my ConTeXt source?


no, because the context script also does some cleanup and checking (like not 
replacing the tuc file when there is an issue)
(letting tex influence its own run is somewhat tricky and has limitations)


Ok, would have been nice. Will write a wrapper script for my use case.


it it's systematic, predictable etc etc we can always add it as option 
but filenames and their use are pretty fragile in epub (i had no 
problems with crashing of locking the kobo)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-20 Thread Henning Hraban Ramm
Am 2015-01-19 um 15:48 schrieb Hans Hagen :

> On 1/17/2015 1:52 PM, Henning Hraban Ramm wrote:
>> * How can I set the current \date in a metadata variable?
>> (I know it’s also in the date tag of , but I know how to format 
>> \date …)
>> 
>> This doesn’t work (i.e. I get „\date“ in XML/XHTML):
>> 
>> \settaggedmetadata[
>>  version={\date}
>> ]
> 
> \the\normalyear-\the\normalmonth-\the\normalday

Thanks, but that’s not the same. Not only because I get „2015-1-20“ and not 
„2015-01-20“.

Is there a way to get „everything“ expanded within \settaggedmetadata ?

>> * Can I influence the directory/file names of the export from within the 
>> source?
>> E.g. if I compile „minimal.tex“, I get minimal-export and minimal-epub
>> The —result switch doesn’t change anything.
> 
> hm, honoring --result is doable but in general i'd like to keep the export 
> quite basic and predictable (the less options the better)

Ok, that means we have no influence on files names at all?

>> * BTW: Can I set —result from within my ConTeXt source?
> 
> no, because the context script also does some cleanup and checking (like not 
> replacing the tuc file when there is an issue)
> (letting tex influence its own run is somewhat tricky and has limitations)

Ok, would have been nice. Will write a wrapper script for my use case.


Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-19 Thread Hans Hagen

On 1/17/2015 1:52 PM, Henning Hraban Ramm wrote:

Hi there,

I started documenting ConTeXt’s current ePub/export behaviour in 
http://wiki.contextgarden.net/ePub and will merge/delete the content of the 
current wiki pages as soon as I’m content with its content ;)

* Do you think it would be better to document export and ePub separately?


Of course I have questions, e.g.:

* How can I set the current \date in a metadata variable?
(I know it’s also in the date tag of , but I know how to format \date 
…)

This doesn’t work (i.e. I get „\date“ in XML/XHTML):

\settaggedmetadata[
version={\date}
]


\the\normalyear-\the\normalmonth-\the\normalday


* Can I influence the directory/file names of the export from within the source?
E.g. if I compile „minimal.tex“, I get minimal-export and minimal-epub
The —result switch doesn’t change anything.


hm, honoring --result is doable but in general i'd like to keep the 
export quite basic and predictable (the less options the better)



* BTW: Can I set —result from within my ConTeXt source?


no, because the context script also does some cleanup and checking (like 
not replacing the tuc file when there is an issue)


(letting tex influence its own run is somewhat tricky and has limitations)

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-18 Thread Henning Hraban Ramm
Am 2015-01-18 um 20:45 schrieb Keith Schultz :

>> I started documenting ConTeXt’s current ePub/export behaviour in 
>> http://wiki.contextgarden.net/ePub and will merge/delete the content of the 
>> current wiki pages as soon as I’m content with its content ;)
>> 
>> * Do you think it would be better to document export and ePub separately?
>> 
>   I think it best that they be handle separately.
>   Especially, if you want to be thorough.

Already did the split after sending my previous message, so there’s now ePub 
and http://wiki.contextgarden.net/Export

I’ll probably create more pages on specific ePub topics like images and cover 
pages.


Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-18 Thread Keith Schultz
Hi Henning,

> Am 17.01.2015 um 13:52 schrieb Henning Hraban Ramm :
> 
> Hi there,
> 
> I started documenting ConTeXt’s current ePub/export behaviour in 
> http://wiki.contextgarden.net/ePub and will merge/delete the content of the 
> current wiki pages as soon as I’m content with its content ;)
> 
> * Do you think it would be better to document export and ePub separately?
> 
I think it best that they be handle separately.
Especially, if you want to be thorough.

regards
Keith.

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-17 Thread Henning Hraban Ramm
Hi there,

I started documenting ConTeXt’s current ePub/export behaviour in 
http://wiki.contextgarden.net/ePub and will merge/delete the content of the 
current wiki pages as soon as I’m content with its content ;)

* Do you think it would be better to document export and ePub separately?


Of course I have questions, e.g.:

* How can I set the current \date in a metadata variable?
(I know it’s also in the date tag of , but I know how to format \date 
…)

This doesn’t work (i.e. I get „\date“ in XML/XHTML):

\settaggedmetadata[
version={\date}
]

* Can I influence the directory/file names of the export from within the source?
E.g. if I compile „minimal.tex“, I get minimal-export and minimal-epub
The —result switch doesn’t change anything.

* BTW: Can I set —result from within my ConTeXt source?

More to follow ;)



Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-13 Thread Henning Hraban Ramm

Am 2015-01-13 um 20:50 schrieb Hans Hagen :

> On 1/13/2015 2:57 PM, Henning Hraban Ramm wrote:
> 
>> mtx-epub| copying coverpage 'giraffe.pdf' to 
>> 'solo-export/giraffe.pdf'...texmf/tex/texmf-context/scripts/context/lua/mtx-epub.lua:557:
>>  bad argument #1 to 'gsub' (string expected, got nil)
>> 
>> 
>> I’ll investigate further tomorrow.
> 
> i'll intercept the missing image

Thanks, but the image isn’t missing!?

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-13 Thread Hans Hagen

On 1/13/2015 2:57 PM, Henning Hraban Ramm wrote:


mtx-epub| copying coverpage 'giraffe.pdf' to 
'solo-export/giraffe.pdf'...texmf/tex/texmf-context/scripts/context/lua/mtx-epub.lua:557:
 bad argument #1 to 'gsub' (string expected, got nil)


I’ll investigate further tomorrow.


i'll intercept the missing image

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-13 Thread Henning Hraban Ramm
Am 2015-01-13 um 15:58 schrieb Hans Hagen :

> the whole generation of epub was cleanup up (already a while ago)

I know, but it seems I have to recreate my whole workflow again.

> just use:
> 
> \setupbackend[export=yes]
> 
> all happens in dedicated sub directories now
> 
> -export
> -epub
> 
> also, there have been some changes in the output (more detail in sectioning 
> and so i.e. chains and levels) ... just look at the files produced
> 
> there is also div based output

Didn’t have enough time to look into everything in detail, but if I just run 
the epub script after the context run, it fails:


$ mtxrun --script epub --make solo

resolvers   | caching | skipping 'files' for 'home:texmf' from 
'/Users/hraban/Library/texmf/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/trees/54be04d87dd160089f572b19cb5c97e9'
 (version mismatch)
mtx-epub| using specification file 'solo-export/solo-pub.lua'
mtx-epub| the 'mudraw' binary is not present
mtx-epub| using cover page 'giraffe.pdf'
mtx-epub| copying coverpage 'giraffe.pdf' to 
'solo-export/giraffe.pdf'...texmf/tex/texmf-context/scripts/context/lua/mtx-epub.lua:557:
 bad argument #1 to 'gsub' (string expected, got nil)


I’ll investigate further tomorrow.

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] What happened to the ePub script?

2015-01-13 Thread Hans Hagen

On 1/13/2015 7:45 AM, Henning Hraban Ramm wrote:

Hi,
with the latest betas, the ePub script doesn’t work anymore.
Regardless with which file I call it, I get only:


the whole generation of epub was cleanup up (already a while ago)


$ mtxrun --script mtx-epub --make solo

resolvers   | caching | skipping 'files' for 'home:texmf' from 
'/Users/hraban/Library/texmf/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/trees/54be04d87dd160089f572b19cb5c97e9'
 (version mismatch)
mtx-epub| unknown specificaton file for 'solo'


Previously, you didn’t need to call 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 One}]

\input tufte

\stopsection

\startsection[title={Section Two}]

\input knuth

\externalfigure[koe][width=\textwidth]

\stopsection

\stopchapter

\stoptext


An export.specification file was previously created by the script, I don’t know 
(anymore) for what. Calling the script with one of those also doesn’t do 
anything.


just use:

\setupbackend[export=yes]

all happens in dedicated sub directories now

-export
-epub

also, there have been some changes in the output (more detail in 
sectioning and so i.e. chains and levels) ... just look at the files 
produced


there is also div based output

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___