dskhrt | 15 Apr 2011 12:04
Picon
Favicon

labelsep in v1.4

Hi, 
I have recently updated my powerdot to v1.4 and get confused with its labelsep settings.
When I compile powerdot-example1.tex by myself, the horizontal space between labels and texts in list
environments (e.g., the space between the square and "Here" in p.4) seems larger than the sample PDF
contained in the installation package.
(My own output seems exactly the same as 
http://stuwww.uvt.nl/~hendri/Downloads/Files/powerdot-example1.pdf
while I refer as the sample PDF to 
http://mirrors.ctan.org/macros/latex/contrib/powerdot/docs/powerdot-example1.pdf
)
This confuses me because the labelsep in my old slides compiled with v1.3 are consistent with the sample PDF
despite that I used default settings.

Could someone please explain whether I should be able to replicate the sample PDF  (i.e., whether my
installation goes wrong or not)? Also, if my installation is all right, is there any way to narrow labelsep
as in the sample PDF without modifying pdsetup in each style file one by one? Thank you very much for your
kind attention.

Sincerely,
Daisuke Hirata 

Pedro Jorge Caridade | 15 Apr 2011 12:32

Re: labelsep in v1.4

Dear Daisuke

Could you send us a example tex and pdf? Also, put a \listfiles
command inside, and send us the outcome.

Pedro

2011/4/15  <dskhrt <at> mail.goo.ne.jp>:
> Hi,
> I have recently updated my powerdot to v1.4 and get confused with its labelsep settings.
> When I compile powerdot-example1.tex by myself, the horizontal space between labels and texts in list
environments (e.g., the space between the square and "Here" in p.4) seems larger than the sample PDF
contained in the installation package.
> (My own output seems exactly the same as
> http://stuwww.uvt.nl/~hendri/Downloads/Files/powerdot-example1.pdf
> while I refer as the sample PDF to
> http://mirrors.ctan.org/macros/latex/contrib/powerdot/docs/powerdot-example1.pdf
> )
> This confuses me because the labelsep in my old slides compiled with v1.3 are consistent with the sample
PDF despite that I used default settings.
>
> Could someone please explain whether I should be able to replicate the sample PDF  (i.e., whether my
installation goes wrong or not)? Also, if my installation is all right, is there any way to narrow labelsep
as in the sample PDF without modifying pdsetup in each style file one by one? Thank you very much for your
kind attention.
>
> Sincerely,
> Daisuke Hirata
>
>
(Continue reading)

D. Hirata | 15 Apr 2011 13:06
Picon
Favicon

Re: labelsep in v1.4

Thank you for your reply.
I attach my files (.tex, .log, .ps) and the sample pdf. Please note that the PDF is NOT created from my source
files but just taken from CTAN. The problem is the difference in labelsep between my ps file and the sample pdf.
Thank you very much again for your attention.

Daisuke

2011/04/15 (Fri) 19:32, "Pedro Jorge Caridade" <caridade <at> qta.qui.uc.pt> wrote:
> Dear Daisuke
> 
> Could you send us a example tex and pdf? Also, put a \listfiles
> command inside, and send us the outcome.
> 
> Pedro
> 
> 
> 2011/4/15  <dskhrt <at> mail.goo.ne.jp>:
> > Hi,
> > I have recently updated my powerdot to v1.4 and get confused with its labelsep settings.
> > When I compile powerdot-example1.tex by myself, the horizontal space between labels and texts in list
environments (e.g., the space between the square and "Here" in p.4) seems larger than the sample PDF
contained in the installation package.
> > (My own output seems exactly the same as
> > http://stuwww.uvt.nl/~hendri/Downloads/Files/powerdot-example1.pdf
> > while I refer as the sample PDF to
> > http://mirrors.ctan.org/macros/latex/contrib/powerdot/docs/powerdot-example1.pdf
> > )
> > This confuses me because the labelsep in my old slides compiled with v1.3 are consistent with the sample
PDF despite that I used default settings.
> >
(Continue reading)

Herbert Voss | 15 Apr 2011 17:20
Picon
Picon
Favicon

Re: labelsep in v1.4

Am 15.04.2011 12:04, schrieb dskhrt <at> mail.goo.ne.jp:

> I have recently updated my powerdot to v1.4 and get confused with its labelsep settings.
> When I compile powerdot-example1.tex by myself, the horizontal space between labels and texts in list
environments (e.g., the space between the square and "Here" in p.4) seems larger than the sample PDF
contained in the installation package.
> (My own output seems exactly the same as
> http://stuwww.uvt.nl/~hendri/Downloads/Files/powerdot-example1.pdf
> while I refer as the sample PDF to
> http://mirrors.ctan.org/macros/latex/contrib/powerdot/docs/powerdot-example1.pdf

I have no idea why the setting of \pdsetup has no effect without
setting \enit <at>  <at> list to undefined. However, try the following:

\documentclass{powerdot}
\makeatletter
\let\enit <at>  <at> list\ <at> undefined
\makeatother
%\pdsetup{list={labelsep=1.2em,itemsep=*,topsep=5pt,parsep=0pt}}
...

With \pdsetup you can set other values

Herbert

D. Hirata | 15 Apr 2011 18:30
Picon
Favicon

Re: labelsep in v1.4

Thanks for your info.
 By the way, where can I download the older version of powerdot so that I can compare the two versions?

Daisuke

2011/04/16 (Sat) 00:20, "Herbert Voss" <Herbert.Voss <at> FU-Berlin.DE> wrote:
> Am 15.04.2011 12:04, schrieb dskhrt <at> mail.goo.ne.jp:
> 
> > I have recently updated my powerdot to v1.4 and get confused with its labelsep settings.
> > When I compile powerdot-example1.tex by myself, the horizontal space between labels and texts in list
environments (e.g., the space between the square and "Here" in p.4) seems larger than the sample PDF
contained in the installation package.
> > (My own output seems exactly the same as
> > http://stuwww.uvt.nl/~hendri/Downloads/Files/powerdot-example1.pdf
> > while I refer as the sample PDF to
> > http://mirrors.ctan.org/macros/latex/contrib/powerdot/docs/powerdot-example1.pdf
> 
> I have no idea why the setting of \pdsetup has no effect without
> setting \enit <at>  <at> list to undefined. However, try the following:
> 
> \documentclass{powerdot}
> \makeatletter
> \let\enit <at>  <at> list\ <at> undefined
> \makeatother
> %\pdsetup{list={labelsep=1.2em,itemsep=*,topsep=5pt,parsep=0pt}}
> ...
> 
> With \pdsetup you can set other values
> 
> Herbert
(Continue reading)

Herbert Voss | 18 Apr 2011 11:18
Picon
Picon
Favicon

Re: labelsep in v1.4

Am 15.04.2011 18:30, schrieb D. Hirata:

>   By the way, where can I download the older version of powerdot so that I can compare the two versions?

http://archiv.dante.de/~herbert/pd1-3.tgz

Herbert

Thomas Uhle | 21 Apr 2011 10:57
Picon

Re: labelsep in v1.4

Herbert Voss wrote:

> I have no idea why the setting of \pdsetup has no effect without
> setting \enit <at>  <at> list to undefined. However, try the following:

I did some investigation because I had the same problem. It arouses from 
different enumitem.sty. This package uses slightly different internal 
macros since version 2.0 on which powerdot unluckily relies. You could
observe this misbehaviour since e.g. TeX Live 2008 which is shipping
enumitem.sty v2.1, and - of course - also with newer releases.

So, one possible solution could be to switch back to enumitem.sty v1.1.
A second solution is to take the latest powerdot.cls v1.4a from CTAN and 
apply my patch that is attached to this e-mail and everything will be 
fine again.

Maybe one of the package maintainers, Hendri Adriaens or Herbert Voss, 
could push an update release of powerdot to CTAN.

Best regards,

Thomas Uhle
Attachment (powerdot.diff): text/x-patch, 1283 bytes
Herbert Voss | 21 Apr 2011 14:14
Picon
Picon
Favicon

Re: labelsep in v1.4

Am 21.04.2011 10:57, schrieb Thomas Uhle:
> Herbert Voss wrote:
>
>> I have no idea why the setting of \pdsetup has no effect without
>> setting \enit <at>  <at> list to undefined. However, try the following:
>
>
> I did some investigation because I had the same problem. It arouses from
> different enumitem.sty. This package uses slightly different internal
> macros since version 2.0 on which powerdot unluckily relies. You could
> observe this misbehaviour since e.g. TeX Live 2008 which is shipping
> enumitem.sty v2.1, and - of course - also with newer releases.
>
> So, one possible solution could be to switch back to enumitem.sty v1.1.
> A second solution is to take the latest powerdot.cls v1.4a from CTAN and
> apply my patch that is attached to this e-mail and everything will be
> fine again.
>
> Maybe one of the package maintainers, Hendri Adriaens or Herbert Voss,
> could push an update release of powerdot to CTAN.

Your changes are already part of the current powerdot.cls

Herbert


Gmane