brandlogo url relative to where compiled

[kcrisman]

It seems that in <docinfo>, the <brandlogo source="..."> attribute is called relative to the directory one compiles in, not to the location of the xml file where the <docinfo> occurs.

That's fine, but if so then it should be documented, since one probably usually will NOT run xsltproc in the same directory as the source in order to avoid cluttering up the source directory with the generated files. Otherwise perhaps this behavior should be changed.

[rbeezer]

This attribute/URL, like for all images, is relative to wherever you host the pages containing the images. Eventually, the HTML will live on a webserver and you should anticipate that scenario. Until then, it is your choice for the local destination of content pages, and directories of images.

Note there is a configurable directory prefix (which maybe I like and maybe I don't).

Short answer: image management is not 100% automatic. Writing some project management scripts early is always a good idea.

I'm open to a suggestion for where to explain this?

[Alex-Jordan]

To close this, I propose someone write a section of the documentation guide that is all about the various things that can go into a docinfo element. Including a brandlogo, which could discuss the issue here.

[kcrisman]

To close this, I propose someone write a section of the documentation guide that is all about the various things that can go into a docinfo element. Including a brandlogo, which could discuss the issue here.

Yes, please! A lot of us who have older projects not using the full capabilities would benefit from this too, and new projects can then get it right from the start.

[rbeezer]

Significant parts of docinfo should migrate to the publisher file.

On 12/10/19 12:17 AM, Alex Jordan wrote:

To close this, I propose someone write a section of the documentation guide that is all about the various things that can go into a |docinfo| element. Including a |brandlogo|, which could discuss the issue here.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rbeezer/mathbook/issues/114?email_source=notifications&email_token=AAOLM4VPQLLDPW4VXKHQUXLQX5GA3A5CNFSM4BJEVUJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGOLQ7Y#issuecomment-563918975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOLM4VQWKMWDSA73RQMLILQX5GA3ANCNFSM4BJEVUJQ.

[davidfarmer]

@kcrisman I think the suggestion was that you write it.

On Tue, 10 Dec 2019, kcrisman wrote:

To close this, I propose someone write a section of the documentation guide that is all about the various things that can go into a docinfo element. Including a brandlogo, which could discuss the issue here.

Yes, please! A lot of us who have older projects not using the full capabilities would benefit from this too, and new projects can then get it right from the start.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, orunsubscribe.[AABTULCQGIH4XPWNHYTFPTTQX6VO7A5CNFSM4BJEVUJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOOR PWSZGOEGPRIAA.gif]

[kcrisman]

@kcrisman I think the suggestion was that you write it.

You are right, I had forgotten that - only saw the replies! Unfortunately in that case it will be some time before it happens :(