Re: [Kicad-developers] asciidoc

2021-06-03 Thread Nick Østergaard 
It was also happy here
https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/jobs/1316881996

tor. 3. jun. 2021 22.38 skrev Steven A. Falco :

> Yes - I had to refresh my token too.  By the way, below is a link to the
> copr test build I made (in my private copr) - it passed :-)
>
> https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/2215757/
>
> Steve
>
> On 6/3/21 4:32 PM, Nick Østergaard wrote:
> > Ah,ok, I misread the pipeline logs..
> >
> > Error: Login invalid/expired. Please visit
> https://copr.fedorainfracloud.org/api <
> https://copr.fedorainfracloud.org/api> to get or renew your API token.
> >
> > I gotta update that.
> >
> > On Thu, 3 Jun 2021 at 22:29, Steven A. Falco  > wrote:
> >
> > The build you are looking at happened before I put in the fix.  In
> other words, I saw that same build failure (on May 30), and put in the fix
> a few hours later.
> >
> > The next doc build should use rubygem-asciidoctor in place of
> asciidoc, and it should pass.
> >
> > Can you kick off a manual build of the docs to test that?
> >
> >  Steve
> >
> > On 6/3/21 3:26 PM, Nick Østergaard wrote:
> >  > @Steven A. Falco >
> >  >
> >  > Did you have a look at building the docs for fedora with the
> other package?
> >  >
> >  > It appears to still BuildRequires: asciidoc when I look in the
> spec file in
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/> <
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/>>
> >  >
> >  > On Sun, 30 May 2021 at 22:51, Jon Evans   >> wrote:
> >  >
> >  > If you use Docker, there is also a container for the docs
> build based on Debian:
> >  >
> >  >
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
> <
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base>
> <
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
> <
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
> >>
> >  >
> >  > Maybe this is also helpful for setting up a Fedora VM or
> Docker container
> >  >
> >  > On Sun, May 30, 2021 at 3:00 PM Steven A. Falco <
> stevenfa...@gmail.com   stevenfa...@gmail.com >> wrote:
> >  >  >
> >  >  > I'll have to spin up a VM to play with that.  I'll get
> back to you... :-)
> >  >  >
> >  >  > Steve
> >  >  >
> >  >  > On 5/30/21 2:34 PM, Jon Evans wrote:
> >  >  > > You want this one:
> https://github.com/Mogztter/asciidoctor-web-pdf <
> https://github.com/Mogztter/asciidoctor-web-pdf> <
> https://github.com/Mogztter/asciidoctor-web-pdf <
> https://github.com/Mogztter/asciidoctor-web-pdf>>
> >  >  > >
> >  >  > > On Ubuntu I install it with "sudo npm i -g
> @asciidoctor/core asciidoctor-pdf"
> >  >  > >
> >  >  > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco <
> stevenfa...@gmail.com   stevenfa...@gmail.com >> wrote:
> >  >  > >>
> >  >  > >> I'm able to build the html pages, which is all we need
> for the nightlies, but I am not able to build the pdf files.  I get an
> error:
> >  >  > >>
> >  >  > >>   Could NOT find ASCIIDOCTORPDF (missing:
> ASCIIDOCTORPDF_COMMAND)
> >  >  > >>
> >  >  > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake
> wants a program called "asciidoctor-web-pdf".
> >  >  > >>
> >  >  > >> Fedora has a package "rubygem-asciidoctor-pdf" which
> provides a program called "asciidoctor-pdf".
> >  >  > >>
> >  >  > >> I don't know if "asciidoctor-pdf" is equivalent to
> "asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept
> either one.
> >  >  > >>
> >  >  > >>  Steve
> >  >  > >>
> >  >  > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> >  >  > >>> Thanks Jon.
> >  >  > >>>
> >  >  > >>> I'm running a test build now.  If it passes, I'll
> propose a patch for the README.  I'll also push the change to the nightly
> Fedora builds.
> >  >  > >>>
> >  >  > >>>   Steve
> >  >  > >>>
> >  >  > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
> >  >  >  Hi Steve,
> >  >  > 
> >  >  >  As the readme notes, I have not yet updated the docs
>

Re: [Kicad-developers] asciidoc

2021-06-03 Thread Steven A. Falco 

Yes - I had to refresh my token too.  By the way, below is a link to the copr 
test build I made (in my private copr) - it passed :-)

https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/2215757/

Steve

On 6/3/21 4:32 PM, Nick Østergaard wrote:

Ah,ok, I misread the pipeline logs..

Error: Login invalid/expired. Please visit https://copr.fedorainfracloud.org/api 
 to get or renew your API token.

I gotta update that.

On Thu, 3 Jun 2021 at 22:29, Steven A. Falco mailto:stevenfa...@gmail.com>> wrote:

The build you are looking at happened before I put in the fix.  In other 
words, I saw that same build failure (on May 30), and put in the fix a few 
hours later.

The next doc build should use rubygem-asciidoctor in place of asciidoc, and 
it should pass.

Can you kick off a manual build of the docs to test that?

         Steve

On 6/3/21 3:26 PM, Nick Østergaard wrote:
 > @Steven A. Falco >
 >
 > Did you have a look at building the docs for fedora with the other 
package?
 >
 > It appears to still BuildRequires: asciidoc when I look in the spec file in 
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ 
 
>
 >
 > On Sun, 30 May 2021 at 22:51, Jon Evans mailto:j...@craftyjon.com> 
>> wrote:
 >
 >     If you use Docker, there is also a container for the docs build 
based on Debian:
 >
 > 
https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
 

 
>
 >
 >     Maybe this is also helpful for setting up a Fedora VM or Docker 
container
 >
 >     On Sun, May 30, 2021 at 3:00 PM Steven A. Falco mailto:stevenfa...@gmail.com> >> wrote:
 >      >
 >      > I'll have to spin up a VM to play with that.  I'll get back to 
you... :-)
 >      >
 >      >         Steve
 >      >
 >      > On 5/30/21 2:34 PM, Jon Evans wrote:
 >      > > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf 
 
>
 >      > >
 >      > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core 
asciidoctor-pdf"
 >      > >
 >      > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco mailto:stevenfa...@gmail.com> >> wrote:
 >      > >>
 >      > >> I'm able to build the html pages, which is all we need for the 
nightlies, but I am not able to build the pdf files.  I get an error:
 >      > >>
 >      > >>           Could NOT find ASCIIDOCTORPDF (missing: 
ASCIIDOCTORPDF_COMMAND)
 >      > >>
 >      > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program 
called "asciidoctor-web-pdf".
 >      > >>
 >      > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides a program 
called "asciidoctor-pdf".
 >      > >>
 >      > >> I don't know if "asciidoctor-pdf" is equivalent to 
"asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept either one.
 >      > >>
 >      > >>          Steve
 >      > >>
 >      > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
 >      > >>> Thanks Jon.
 >      > >>>
 >      > >>> I'm running a test build now.  If it passes, I'll propose a 
patch for the README.  I'll also push the change to the nightly Fedora builds.
 >      > >>>
 >      > >>>       Steve
 >      > >>>
 >      > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
 >      >  Hi Steve,
 >      > 
 >      >  As the readme notes, I have not yet updated the docs for 
Fedora or
 >      >  Manjaro/Arch as I don't use those distros and am not sure of 
the right
 >      >  incantations.
 >      > 
 >      >  If you can advise what should go into the README I'm happy 
to update it.
 >      > 
 >      >  Also, please let me know if you run into any snags building 
the docs
 >      >  with the new toolchain.
 >      > 
 >      >  Best,
 >      >  Jon
 >      > 
 >      >

Re: [Kicad-developers] asciidoc

2021-06-03 Thread Nick Østergaard 
Hopefully it should be running ok in
https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/jobs/1316881996

On Thu, 3 Jun 2021 at 22:32, Nick Østergaard  wrote:

> Ah,ok, I misread the pipeline logs..
>
> Error: Login invalid/expired. Please visit
> https://copr.fedorainfracloud.org/api to get or renew your API token.
>
> I gotta update that.
>
> On Thu, 3 Jun 2021 at 22:29, Steven A. Falco 
> wrote:
>
>> The build you are looking at happened before I put in the fix.  In other
>> words, I saw that same build failure (on May 30), and put in the fix a few
>> hours later.
>>
>> The next doc build should use rubygem-asciidoctor in place of asciidoc,
>> and it should pass.
>>
>> Can you kick off a manual build of the docs to test that?
>>
>> Steve
>>
>> On 6/3/21 3:26 PM, Nick Østergaard wrote:
>> > @Steven A. Falco 
>> >
>> > Did you have a look at building the docs for fedora with the other
>> package?
>> >
>> > It appears to still BuildRequires: asciidoc when I look in the spec
>> file in
>> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <
>> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/>
>> >
>> > On Sun, 30 May 2021 at 22:51, Jon Evans > j...@craftyjon.com>> wrote:
>> >
>> > If you use Docker, there is also a container for the docs build
>> based on Debian:
>> >
>> >
>> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
>> <
>> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
>> >
>> >
>> > Maybe this is also helpful for setting up a Fedora VM or Docker
>> container
>> >
>> > On Sun, May 30, 2021 at 3:00 PM Steven A. Falco <
>> stevenfa...@gmail.com > wrote:
>> >  >
>> >  > I'll have to spin up a VM to play with that.  I'll get back to
>> you... :-)
>> >  >
>> >  > Steve
>> >  >
>> >  > On 5/30/21 2:34 PM, Jon Evans wrote:
>> >  > > You want this one:
>> https://github.com/Mogztter/asciidoctor-web-pdf <
>> https://github.com/Mogztter/asciidoctor-web-pdf>
>> >  > >
>> >  > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core
>> asciidoctor-pdf"
>> >  > >
>> >  > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco <
>> stevenfa...@gmail.com > wrote:
>> >  > >>
>> >  > >> I'm able to build the html pages, which is all we need for
>> the nightlies, but I am not able to build the pdf files.  I get an error:
>> >  > >>
>> >  > >>   Could NOT find ASCIIDOCTORPDF (missing:
>> ASCIIDOCTORPDF_COMMAND)
>> >  > >>
>> >  > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a
>> program called "asciidoctor-web-pdf".
>> >  > >>
>> >  > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides
>> a program called "asciidoctor-pdf".
>> >  > >>
>> >  > >> I don't know if "asciidoctor-pdf" is equivalent to
>> "asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept
>> either one.
>> >  > >>
>> >  > >>  Steve
>> >  > >>
>> >  > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
>> >  > >>> Thanks Jon.
>> >  > >>>
>> >  > >>> I'm running a test build now.  If it passes, I'll propose a
>> patch for the README.  I'll also push the change to the nightly Fedora
>> builds.
>> >  > >>>
>> >  > >>>   Steve
>> >  > >>>
>> >  > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
>> >  >  Hi Steve,
>> >  > 
>> >  >  As the readme notes, I have not yet updated the docs for
>> Fedora or
>> >  >  Manjaro/Arch as I don't use those distros and am not sure
>> of the right
>> >  >  incantations.
>> >  > 
>> >  >  If you can advise what should go into the README I'm happy
>> to update it.
>> >  > 
>> >  >  Also, please let me know if you run into any snags building
>> the docs
>> >  >  with the new toolchain.
>> >  > 
>> >  >  Best,
>> >  >  Jon
>> >  > 
>> >  >  On Sun, May 30, 2021 at 1:49 PM Steven A. Falco <
>> stevenfa...@gmail.com > wrote:
>> >  > >
>> >  > > The Fedora nightly build for doc failed because it wanted
>> asciidoctor, but all it had was asciidoc.
>> >  > >
>> >  > > I believe I just need to change the "buildrequires" from:
>> >  > >
>> >  > > BuildRequires:  asciidoc
>> >  > >
>> >  > > to:
>> >  > >
>> >  > > BuildRequires:  rubygem-asciidoctor
>> >  > >
>> >  > > in the kicad-nightly-doc.spec file.
>> >  > >
>> >  > > However, I also noticed that the page
>> https://gitlab.com/kicad/services/kicad-doc <
>> https://gitlab.com/kicad/services/kicad-doc> still calls for asciidoc,
>> so that README.adoc should probably be

Re: [Kicad-developers] asciidoc

2021-06-03 Thread Nick Østergaard 
Ah,ok, I misread the pipeline logs..

Error: Login invalid/expired. Please visit
https://copr.fedorainfracloud.org/api to get or renew your API token.

I gotta update that.

On Thu, 3 Jun 2021 at 22:29, Steven A. Falco  wrote:

> The build you are looking at happened before I put in the fix.  In other
> words, I saw that same build failure (on May 30), and put in the fix a few
> hours later.
>
> The next doc build should use rubygem-asciidoctor in place of asciidoc,
> and it should pass.
>
> Can you kick off a manual build of the docs to test that?
>
> Steve
>
> On 6/3/21 3:26 PM, Nick Østergaard wrote:
> > @Steven A. Falco 
> >
> > Did you have a look at building the docs for fedora with the other
> package?
> >
> > It appears to still BuildRequires: asciidoc when I look in the spec file
> in https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ <
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/>
> >
> > On Sun, 30 May 2021 at 22:51, Jon Evans  j...@craftyjon.com>> wrote:
> >
> > If you use Docker, there is also a container for the docs build
> based on Debian:
> >
> >
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
> <
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
> >
> >
> > Maybe this is also helpful for setting up a Fedora VM or Docker
> container
> >
> > On Sun, May 30, 2021 at 3:00 PM Steven A. Falco <
> stevenfa...@gmail.com > wrote:
> >  >
> >  > I'll have to spin up a VM to play with that.  I'll get back to
> you... :-)
> >  >
> >  > Steve
> >  >
> >  > On 5/30/21 2:34 PM, Jon Evans wrote:
> >  > > You want this one:
> https://github.com/Mogztter/asciidoctor-web-pdf <
> https://github.com/Mogztter/asciidoctor-web-pdf>
> >  > >
> >  > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core
> asciidoctor-pdf"
> >  > >
> >  > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco <
> stevenfa...@gmail.com > wrote:
> >  > >>
> >  > >> I'm able to build the html pages, which is all we need for the
> nightlies, but I am not able to build the pdf files.  I get an error:
> >  > >>
> >  > >>   Could NOT find ASCIIDOCTORPDF (missing:
> ASCIIDOCTORPDF_COMMAND)
> >  > >>
> >  > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a
> program called "asciidoctor-web-pdf".
> >  > >>
> >  > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides
> a program called "asciidoctor-pdf".
> >  > >>
> >  > >> I don't know if "asciidoctor-pdf" is equivalent to
> "asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept
> either one.
> >  > >>
> >  > >>  Steve
> >  > >>
> >  > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> >  > >>> Thanks Jon.
> >  > >>>
> >  > >>> I'm running a test build now.  If it passes, I'll propose a
> patch for the README.  I'll also push the change to the nightly Fedora
> builds.
> >  > >>>
> >  > >>>   Steve
> >  > >>>
> >  > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
> >  >  Hi Steve,
> >  > 
> >  >  As the readme notes, I have not yet updated the docs for
> Fedora or
> >  >  Manjaro/Arch as I don't use those distros and am not sure of
> the right
> >  >  incantations.
> >  > 
> >  >  If you can advise what should go into the README I'm happy
> to update it.
> >  > 
> >  >  Also, please let me know if you run into any snags building
> the docs
> >  >  with the new toolchain.
> >  > 
> >  >  Best,
> >  >  Jon
> >  > 
> >  >  On Sun, May 30, 2021 at 1:49 PM Steven A. Falco <
> stevenfa...@gmail.com > wrote:
> >  > >
> >  > > The Fedora nightly build for doc failed because it wanted
> asciidoctor, but all it had was asciidoc.
> >  > >
> >  > > I believe I just need to change the "buildrequires" from:
> >  > >
> >  > > BuildRequires:  asciidoc
> >  > >
> >  > > to:
> >  > >
> >  > > BuildRequires:  rubygem-asciidoctor
> >  > >
> >  > > in the kicad-nightly-doc.spec file.
> >  > >
> >  > > However, I also noticed that the page
> https://gitlab.com/kicad/services/kicad-doc <
> https://gitlab.com/kicad/services/kicad-doc> still calls for asciidoc, so
> that README.adoc should probably be updated too.
> >  > >
> >  > >   Steve
> >  > >
> >  > >
> >  > >
> >  > > ___
> >  > > Mailing list: https://launchpad.net/~kicad-developers <
> https://launchpad.net/~kicad-developers>
> >  >

Re: [Kicad-developers] asciidoc

2021-06-03 Thread Steven A. Falco 

The build you are looking at happened before I put in the fix.  In other words, 
I saw that same build failure (on May 30), and put in the fix a few hours later.

The next doc build should use rubygem-asciidoctor in place of asciidoc, and it 
should pass.

Can you kick off a manual build of the docs to test that?

Steve

On 6/3/21 3:26 PM, Nick Østergaard wrote:

@Steven A. Falco 

Did you have a look at building the docs for fedora with the other package?

It appears to still BuildRequires: asciidoc when I look in the spec file in 
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/ 


On Sun, 30 May 2021 at 22:51, Jon Evans mailto:j...@craftyjon.com>> wrote:

If you use Docker, there is also a container for the docs build based on 
Debian:


https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
 


Maybe this is also helpful for setting up a Fedora VM or Docker container

On Sun, May 30, 2021 at 3:00 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote:
 >
 > I'll have to spin up a VM to play with that.  I'll get back to you... :-)
 >
 >         Steve
 >
 > On 5/30/21 2:34 PM, Jon Evans wrote:
 > > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf 

 > >
 > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core 
asciidoctor-pdf"
 > >
 > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote:
 > >>
 > >> I'm able to build the html pages, which is all we need for the 
nightlies, but I am not able to build the pdf files.  I get an error:
 > >>
 > >>           Could NOT find ASCIIDOCTORPDF (missing: 
ASCIIDOCTORPDF_COMMAND)
 > >>
 > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called 
"asciidoctor-web-pdf".
 > >>
 > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides a program called 
"asciidoctor-pdf".
 > >>
 > >> I don't know if "asciidoctor-pdf" is equivalent to 
"asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept either one.
 > >>
 > >>          Steve
 > >>
 > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
 > >>> Thanks Jon.
 > >>>
 > >>> I'm running a test build now.  If it passes, I'll propose a patch 
for the README.  I'll also push the change to the nightly Fedora builds.
 > >>>
 > >>>       Steve
 > >>>
 > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
 >  Hi Steve,
 > 
 >  As the readme notes, I have not yet updated the docs for Fedora or
 >  Manjaro/Arch as I don't use those distros and am not sure of the 
right
 >  incantations.
 > 
 >  If you can advise what should go into the README I'm happy to 
update it.
 > 
 >  Also, please let me know if you run into any snags building the docs
 >  with the new toolchain.
 > 
 >  Best,
 >  Jon
 > 
 >  On Sun, May 30, 2021 at 1:49 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote:
 > >
 > > The Fedora nightly build for doc failed because it wanted 
asciidoctor, but all it had was asciidoc.
 > >
 > > I believe I just need to change the "buildrequires" from:
 > >
 > > BuildRequires:  asciidoc
 > >
 > > to:
 > >
 > > BuildRequires:  rubygem-asciidoctor
 > >
 > > in the kicad-nightly-doc.spec file.
 > >
 > > However, I also noticed that the page 
https://gitlab.com/kicad/services/kicad-doc  still 
calls for asciidoc, so that README.adoc should probably be updated too.
 > >
 > >           Steve
 > >
 > >
 > >
 > > ___
 > > Mailing list: https://launchpad.net/~kicad-developers 

 > > Post to     : kicad-developers@lists.launchpad.net 

 > > Unsubscribe : https://launchpad.net/~kicad-developers 

 > > More help   : https://help.launchpad.net/ListHelp 

 > >>>
 > >>
 >

___
Mailing list: https://launchpad.net/~kicad-developers 

Post to     : kicad-developers@lists.launchpad.net 

Unsubscribe : https://launchpad.net/~kicad-developers

Re: [Kicad-developers] asciidoc

2021-06-03 Thread Nick Østergaard 
@Steven A. Falco 

Did you have a look at building the docs for fedora with the other package?

It appears to still BuildRequires: asciidoc when I look in the spec file in
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/2215751/

On Sun, 30 May 2021 at 22:51, Jon Evans  wrote:

> If you use Docker, there is also a container for the docs build based on
> Debian:
>
>
> https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base
>
> Maybe this is also helpful for setting up a Fedora VM or Docker container
>
> On Sun, May 30, 2021 at 3:00 PM Steven A. Falco 
> wrote:
> >
> > I'll have to spin up a VM to play with that.  I'll get back to you... :-)
> >
> > Steve
> >
> > On 5/30/21 2:34 PM, Jon Evans wrote:
> > > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf
> > >
> > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core
> asciidoctor-pdf"
> > >
> > > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco 
> wrote:
> > >>
> > >> I'm able to build the html pages, which is all we need for the
> nightlies, but I am not able to build the pdf files.  I get an error:
> > >>
> > >>   Could NOT find ASCIIDOCTORPDF (missing:
> ASCIIDOCTORPDF_COMMAND)
> > >>
> > >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program
> called "asciidoctor-web-pdf".
> > >>
> > >> Fedora has a package "rubygem-asciidoctor-pdf" which provides a
> program called "asciidoctor-pdf".
> > >>
> > >> I don't know if "asciidoctor-pdf" is equivalent to
> "asciidoctor-web-pdf".  If it is, then perhaps the cmake file should accept
> either one.
> > >>
> > >>  Steve
> > >>
> > >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> > >>> Thanks Jon.
> > >>>
> > >>> I'm running a test build now.  If it passes, I'll propose a patch
> for the README.  I'll also push the change to the nightly Fedora builds.
> > >>>
> > >>>   Steve
> > >>>
> > >>> On 5/30/21 1:51 PM, Jon Evans wrote:
> >  Hi Steve,
> > 
> >  As the readme notes, I have not yet updated the docs for Fedora or
> >  Manjaro/Arch as I don't use those distros and am not sure of the
> right
> >  incantations.
> > 
> >  If you can advise what should go into the README I'm happy to
> update it.
> > 
> >  Also, please let me know if you run into any snags building the docs
> >  with the new toolchain.
> > 
> >  Best,
> >  Jon
> > 
> >  On Sun, May 30, 2021 at 1:49 PM Steven A. Falco <
> stevenfa...@gmail.com> wrote:
> > >
> > > The Fedora nightly build for doc failed because it wanted
> asciidoctor, but all it had was asciidoc.
> > >
> > > I believe I just need to change the "buildrequires" from:
> > >
> > > BuildRequires:  asciidoc
> > >
> > > to:
> > >
> > > BuildRequires:  rubygem-asciidoctor
> > >
> > > in the kicad-nightly-doc.spec file.
> > >
> > > However, I also noticed that the page
> https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so
> that README.adoc should probably be updated too.
> > >
> > >   Steve
> > >
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help   : https://help.launchpad.net/ListHelp
> > >>>
> > >>
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Carsten Schoenert 
Hi,

this topic more relevant for kicad-doc I think.

Am 30.05.21 um 20:34 schrieb Jon Evans:
> You want this one: https://github.com/Mogztter/asciidoctor-web-pdf
> 
> On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf"

For Debian (and also for Ubuntu) this isn't possible.
We need to build stuff from packages that are available within the
archive, there is no access to any external resources while binary
package build.

This NPM module isn't packed so we can't use this way.

Some similar Ruby based package is available, but I've no clue if this
is suitable.

> $ apt search asciidoctor
> Sorting... Done
> Full Text Search... Done
> asciidoctor/testing,testing,now 2.0.12-2 all [installed]
>   AsciiDoc to HTML rendering for Ruby
> 
> asciidoctor-doc/testing,testing 2.0.12-2 all
>   AsciiDoc to HTML rendering for Ruby (documentation)
> 
> ruby-asciidoctor/testing,testing,now 2.0.12-2 all [installed,automatic]
>   AsciiDoc to HTML rendering for Ruby (core libraries)
> 
> ruby-asciidoctor-include-ext/testing,testing 0.3.1-2 all
>   Asciidoctor's standard include::[] processor reimplemented as an extension
> 
> ruby-asciidoctor-kroki/testing,testing 0.2.2-3 all
>   Asciidoctor extension to convert diagrams to images using Kroki
> 
> ruby-asciidoctor-pdf/testing,testing,now 1.5.4-3 all [installed]
>   Converts AsciiDoc documents to PDF using Prawn
> 
> ruby-asciidoctor-plantuml/testing,testing 0.0.12-1 all
>   extension for Asciidoctor to enable support for PlantUML diagrams
> 
> $ apt show ruby-asciidoctor-pdf
> Package: ruby-asciidoctor-pdf
> Version: 1.5.4-3
> Priority: optional
> Section: ruby
> Maintainer: Keith Packard 
> Installed-Size: 3.754 kB
> Depends: ruby (>= 1:2.5.1), ruby-asciidoctor (>= 1.5.0), ruby-concurrent (>= 
> 1.1~), ruby-prawn (>= 2.2.0), ruby-prawn-icon (>= 1.4.0), ruby-prawn-svg (>= 
> 0.31.0), ruby-prawn-table (>= 0.2.2), ruby-safe-yaml (>= 1.0.4), 
> ruby-thread-safe (>= 0.3.6), ruby-treetop (>= 1.5.3)
> Suggests: ruby-rouge
> Homepage: https://github.com/asciidoctor/asciidoctor-pdf
> Ruby-Versions: all
> Download-Size: 1.393 kB
> APT-Manual-Installed: yes
> APT-Sources: http://ftp.de.debian.org/debian testing/main amd64 Packages
> Description: Converts AsciiDoc documents to PDF using Prawn
>  An extension for Asciidoctor that converts AsciiDoc documents to PDF
>  using the Prawn PDF library.

-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Jon Evans 
If you use Docker, there is also a container for the docs build based on Debian:

https://gitlab.com/kicad/services/kicad-doc/-/blob/master/utils/docker/Dockerfile.kicad-doc-builder-base

Maybe this is also helpful for setting up a Fedora VM or Docker container

On Sun, May 30, 2021 at 3:00 PM Steven A. Falco  wrote:
>
> I'll have to spin up a VM to play with that.  I'll get back to you... :-)
>
> Steve
>
> On 5/30/21 2:34 PM, Jon Evans wrote:
> > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf
> >
> > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core 
> > asciidoctor-pdf"
> >
> > On Sun, May 30, 2021 at 2:33 PM Steven A. Falco  
> > wrote:
> >>
> >> I'm able to build the html pages, which is all we need for the nightlies, 
> >> but I am not able to build the pdf files.  I get an error:
> >>
> >>   Could NOT find ASCIIDOCTORPDF (missing: ASCIIDOCTORPDF_COMMAND)
> >>
> >> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called 
> >> "asciidoctor-web-pdf".
> >>
> >> Fedora has a package "rubygem-asciidoctor-pdf" which provides a program 
> >> called "asciidoctor-pdf".
> >>
> >> I don't know if "asciidoctor-pdf" is equivalent to "asciidoctor-web-pdf".  
> >> If it is, then perhaps the cmake file should accept either one.
> >>
> >>  Steve
> >>
> >> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> >>> Thanks Jon.
> >>>
> >>> I'm running a test build now.  If it passes, I'll propose a patch for the 
> >>> README.  I'll also push the change to the nightly Fedora builds.
> >>>
> >>>   Steve
> >>>
> >>> On 5/30/21 1:51 PM, Jon Evans wrote:
>  Hi Steve,
> 
>  As the readme notes, I have not yet updated the docs for Fedora or
>  Manjaro/Arch as I don't use those distros and am not sure of the right
>  incantations.
> 
>  If you can advise what should go into the README I'm happy to update it.
> 
>  Also, please let me know if you run into any snags building the docs
>  with the new toolchain.
> 
>  Best,
>  Jon
> 
>  On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  
>  wrote:
> >
> > The Fedora nightly build for doc failed because it wanted asciidoctor, 
> > but all it had was asciidoc.
> >
> > I believe I just need to change the "buildrequires" from:
> >
> > BuildRequires:  asciidoc
> >
> > to:
> >
> > BuildRequires:  rubygem-asciidoctor
> >
> > in the kicad-nightly-doc.spec file.
> >
> > However, I also noticed that the page 
> > https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, 
> > so that README.adoc should probably be updated too.
> >
> >   Steve
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Steven A. Falco 

I'll have to spin up a VM to play with that.  I'll get back to you... :-)

Steve

On 5/30/21 2:34 PM, Jon Evans wrote:

You want this one: https://github.com/Mogztter/asciidoctor-web-pdf

On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf"

On Sun, May 30, 2021 at 2:33 PM Steven A. Falco  wrote:


I'm able to build the html pages, which is all we need for the nightlies, but I 
am not able to build the pdf files.  I get an error:

  Could NOT find ASCIIDOCTORPDF (missing: ASCIIDOCTORPDF_COMMAND)

It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called 
"asciidoctor-web-pdf".

Fedora has a package "rubygem-asciidoctor-pdf" which provides a program called 
"asciidoctor-pdf".

I don't know if "asciidoctor-pdf" is equivalent to "asciidoctor-web-pdf".  If 
it is, then perhaps the cmake file should accept either one.

 Steve

On 5/30/21 1:58 PM, Steven A. Falco wrote:

Thanks Jon.

I'm running a test build now.  If it passes, I'll propose a patch for the 
README.  I'll also push the change to the nightly Fedora builds.

  Steve

On 5/30/21 1:51 PM, Jon Evans wrote:

Hi Steve,

As the readme notes, I have not yet updated the docs for Fedora or
Manjaro/Arch as I don't use those distros and am not sure of the right
incantations.

If you can advise what should go into the README I'm happy to update it.

Also, please let me know if you run into any snags building the docs
with the new toolchain.

Best,
Jon

On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  wrote:


The Fedora nightly build for doc failed because it wanted asciidoctor, but all 
it had was asciidoc.

I believe I just need to change the "buildrequires" from:

BuildRequires:  asciidoc

to:

BuildRequires:  rubygem-asciidoctor

in the kicad-nightly-doc.spec file.

However, I also noticed that the page 
https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so that 
README.adoc should probably be updated too.

  Steve



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp







___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Jon Evans 
You want this one: https://github.com/Mogztter/asciidoctor-web-pdf

On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf"

On Sun, May 30, 2021 at 2:33 PM Steven A. Falco  wrote:
>
> I'm able to build the html pages, which is all we need for the nightlies, but 
> I am not able to build the pdf files.  I get an error:
>
>  Could NOT find ASCIIDOCTORPDF (missing: ASCIIDOCTORPDF_COMMAND)
>
> It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called 
> "asciidoctor-web-pdf".
>
> Fedora has a package "rubygem-asciidoctor-pdf" which provides a program 
> called "asciidoctor-pdf".
>
> I don't know if "asciidoctor-pdf" is equivalent to "asciidoctor-web-pdf".  If 
> it is, then perhaps the cmake file should accept either one.
>
> Steve
>
> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> > Thanks Jon.
> >
> > I'm running a test build now.  If it passes, I'll propose a patch for the 
> > README.  I'll also push the change to the nightly Fedora builds.
> >
> >  Steve
> >
> > On 5/30/21 1:51 PM, Jon Evans wrote:
> >> Hi Steve,
> >>
> >> As the readme notes, I have not yet updated the docs for Fedora or
> >> Manjaro/Arch as I don't use those distros and am not sure of the right
> >> incantations.
> >>
> >> If you can advise what should go into the README I'm happy to update it.
> >>
> >> Also, please let me know if you run into any snags building the docs
> >> with the new toolchain.
> >>
> >> Best,
> >> Jon
> >>
> >> On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  
> >> wrote:
> >>>
> >>> The Fedora nightly build for doc failed because it wanted asciidoctor, 
> >>> but all it had was asciidoc.
> >>>
> >>> I believe I just need to change the "buildrequires" from:
> >>>
> >>> BuildRequires:  asciidoc
> >>>
> >>> to:
> >>>
> >>> BuildRequires:  rubygem-asciidoctor
> >>>
> >>> in the kicad-nightly-doc.spec file.
> >>>
> >>> However, I also noticed that the page 
> >>> https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so 
> >>> that README.adoc should probably be updated too.
> >>>
> >>>  Steve
> >>>
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Steven A. Falco 

I'm able to build the html pages, which is all we need for the nightlies, but I 
am not able to build the pdf files.  I get an error:

Could NOT find ASCIIDOCTORPDF (missing: ASCIIDOCTORPDF_COMMAND)

It looks like CMakeModules/FindASCIIDOCTORPDF.cmake wants a program called 
"asciidoctor-web-pdf".

Fedora has a package "rubygem-asciidoctor-pdf" which provides a program called 
"asciidoctor-pdf".

I don't know if "asciidoctor-pdf" is equivalent to "asciidoctor-web-pdf".  If 
it is, then perhaps the cmake file should accept either one.

Steve

On 5/30/21 1:58 PM, Steven A. Falco wrote:

Thanks Jon.

I'm running a test build now.  If it passes, I'll propose a patch for the 
README.  I'll also push the change to the nightly Fedora builds.

 Steve

On 5/30/21 1:51 PM, Jon Evans wrote:

Hi Steve,

As the readme notes, I have not yet updated the docs for Fedora or
Manjaro/Arch as I don't use those distros and am not sure of the right
incantations.

If you can advise what should go into the README I'm happy to update it.

Also, please let me know if you run into any snags building the docs
with the new toolchain.

Best,
Jon

On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  wrote:


The Fedora nightly build for doc failed because it wanted asciidoctor, but all 
it had was asciidoc.

I believe I just need to change the "buildrequires" from:

BuildRequires:  asciidoc

to:

BuildRequires:  rubygem-asciidoctor

in the kicad-nightly-doc.spec file.

However, I also noticed that the page 
https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so that 
README.adoc should probably be updated too.

 Steve



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Steven A. Falco 

Thanks Jon.

I'm running a test build now.  If it passes, I'll propose a patch for the 
README.  I'll also push the change to the nightly Fedora builds.

Steve

On 5/30/21 1:51 PM, Jon Evans wrote:

Hi Steve,

As the readme notes, I have not yet updated the docs for Fedora or
Manjaro/Arch as I don't use those distros and am not sure of the right
incantations.

If you can advise what should go into the README I'm happy to update it.

Also, please let me know if you run into any snags building the docs
with the new toolchain.

Best,
Jon

On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  wrote:


The Fedora nightly build for doc failed because it wanted asciidoctor, but all 
it had was asciidoc.

I believe I just need to change the "buildrequires" from:

BuildRequires:  asciidoc

to:

BuildRequires:  rubygem-asciidoctor

in the kicad-nightly-doc.spec file.

However, I also noticed that the page 
https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so that 
README.adoc should probably be updated too.

 Steve



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] asciidoc

2021-05-30 Thread Jon Evans 
Hi Steve,

As the readme notes, I have not yet updated the docs for Fedora or
Manjaro/Arch as I don't use those distros and am not sure of the right
incantations.

If you can advise what should go into the README I'm happy to update it.

Also, please let me know if you run into any snags building the docs
with the new toolchain.

Best,
Jon

On Sun, May 30, 2021 at 1:49 PM Steven A. Falco  wrote:
>
> The Fedora nightly build for doc failed because it wanted asciidoctor, but 
> all it had was asciidoc.
>
> I believe I just need to change the "buildrequires" from:
>
> BuildRequires:  asciidoc
>
> to:
>
> BuildRequires:  rubygem-asciidoctor
>
> in the kicad-nightly-doc.spec file.
>
> However, I also noticed that the page 
> https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so that 
> README.adoc should probably be updated too.
>
> Steve
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] asciidoc

2021-05-30 Thread Steven A. Falco 

The Fedora nightly build for doc failed because it wanted asciidoctor, but all 
it had was asciidoc.

I believe I just need to change the "buildrequires" from:

BuildRequires:  asciidoc

to:

BuildRequires:  rubygem-asciidoctor

in the kicad-nightly-doc.spec file.

However, I also noticed that the page 
https://gitlab.com/kicad/services/kicad-doc still calls for asciidoc, so that 
README.adoc should probably be updated too.

Steve



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-12 Thread Wayne Stambaugh 
Thanks Mark!  I'll file this away for future reference.

On 11/12/2017 10:07 AM, Mark Roszko wrote:
> FYI, here's how you add icons
> 
> https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e
> 
> Never did figure out how to make hugo set global asciidoc parameters
> 
> On Fri, Nov 10, 2017 at 2:28 PM, Wayne Stambaugh  > wrote:
> 
> I was hoping the icon would draw user's attention to the warning to the
> obvious backup your files statement but maybe I was being a bit
> optimistic.  I'm fine with it the way it is.  I just wanted to be sure I
> didn't do anything wrong.
> 
> On 11/10/2017 08:48 AM, Nick Østergaard wrote:
> > The source and generated code looks correct. It just seems like we don't
> > have any definition for the admonitionblock div classes for the icons in
> > the CSS. I guess this is a matter of taste, on whether one likes icons
> > or text. I guess icons was not implemented because we didn't use many of
> > these admonition blocks at the time of devising the new site template.
> >
> > 2017-11-10 14:20 GMT+01:00 Wayne Stambaugh  
> > >>:
> >
> >     Maybe one of our resident asciidoc experts can help me out.  I used 
> a
> >     WARNING admonition in the kicad website symbol library table blog
> >     post[1].  I was expecting to see the warning icon per the asciidoc
> >     documentation[2] but I only see a "WARNING" string where I expected 
> the
> >     icon.  Am I doing something wrong here[3] or do we not have our 
> asciidoc
> >     generator configured to use the icons for admonitions?  Thanks in
> >     advance for the help.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     [1]: http://kicad-pcb.org/post/symbol-lib-table/
> 
> >      >
> >     [2]: http://asciidoc.org/userguide.html#X22
> 
> >      >
> >     [3]:
> >     
> https://raw.githubusercontent.com/KiCad/kicad-website/master/content/post/symbol-lib-table.adoc
> 
> 
> >     
>  
> >
> >
> >     ___
> >     Mailing list: https://launchpad.net/~kicad-developers
> 
> >      >
> >     Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >      >
> >     More help   : https://help.launchpad.net/ListHelp
> 
> >      >
> >
> >
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> 
> -- 
> Mark

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-12 Thread Mark Roszko 
FYI, here's how you add icons

https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e

Never did figure out how to make hugo set global asciidoc parameters

On Fri, Nov 10, 2017 at 2:28 PM, Wayne Stambaugh 
wrote:

> I was hoping the icon would draw user's attention to the warning to the
> obvious backup your files statement but maybe I was being a bit
> optimistic.  I'm fine with it the way it is.  I just wanted to be sure I
> didn't do anything wrong.
>
> On 11/10/2017 08:48 AM, Nick Østergaard wrote:
> > The source and generated code looks correct. It just seems like we don't
> > have any definition for the admonitionblock div classes for the icons in
> > the CSS. I guess this is a matter of taste, on whether one likes icons
> > or text. I guess icons was not implemented because we didn't use many of
> > these admonition blocks at the time of devising the new site template.
> >
> > 2017-11-10 14:20 GMT+01:00 Wayne Stambaugh  > >:
> >
> > Maybe one of our resident asciidoc experts can help me out.  I used a
> > WARNING admonition in the kicad website symbol library table blog
> > post[1].  I was expecting to see the warning icon per the asciidoc
> > documentation[2] but I only see a "WARNING" string where I expected
> the
> > icon.  Am I doing something wrong here[3] or do we not have our
> asciidoc
> > generator configured to use the icons for admonitions?  Thanks in
> > advance for the help.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]: http://kicad-pcb.org/post/symbol-lib-table/
> > 
> > [2]: http://asciidoc.org/userguide.html#X22
> > 
> > [3]:
> > https://raw.githubusercontent.com/KiCad/kicad-website/
> master/content/post/symbol-lib-table.adoc
> >  kicad-website/master/content/post/symbol-lib-table.adoc>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > More help   : https://help.launchpad.net/ListHelp
> > 
> >
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Mark
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-11 Thread Marco Ciampa 
On Sat, Nov 11, 2017 at 01:46:07PM +0100, Marco Ciampa wrote:
> On Fri, Nov 10, 2017 at 08:20:32AM -0500, Wayne Stambaugh wrote:
> > Maybe one of our resident asciidoc experts can help me out.  I used a
> > WARNING admonition in the kicad website symbol library table blog
> > post[1].  I was expecting to see the warning icon per the asciidoc
> > documentation[2] but I only see a "WARNING" string where I expected the
> > icon.  Am I doing something wrong here[3] or do we not have our asciidoc
> > generator configured to use the icons for admonitions?  Thanks in
> > advance for the help.
> > 
> > Cheers,
> > 
> > Wayne
> > 
> > [1]: http://kicad-pcb.org/post/symbol-lib-table/
> > [2]: http://asciidoc.org/userguide.html#X22
> > [3]:
> > https://raw.githubusercontent.com/KiCad/kicad-website/master/content/post/symbol-lib-table.adoc
> 
> BTW: no icons are shown on the bottom of the (blog) page ...

Please ignore the previous message.

New version of uBlock add-on for Firefox blocks some icons - don't know why.
Sorry for the noise...

Regards,

--

Marco Ciampa



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-11 Thread Marco Ciampa 
On Fri, Nov 10, 2017 at 08:20:32AM -0500, Wayne Stambaugh wrote:
> Maybe one of our resident asciidoc experts can help me out.  I used a
> WARNING admonition in the kicad website symbol library table blog
> post[1].  I was expecting to see the warning icon per the asciidoc
> documentation[2] but I only see a "WARNING" string where I expected the
> icon.  Am I doing something wrong here[3] or do we not have our asciidoc
> generator configured to use the icons for admonitions?  Thanks in
> advance for the help.
> 
> Cheers,
> 
> Wayne
> 
> [1]: http://kicad-pcb.org/post/symbol-lib-table/
> [2]: http://asciidoc.org/userguide.html#X22
> [3]:
> https://raw.githubusercontent.com/KiCad/kicad-website/master/content/post/symbol-lib-table.adoc

BTW: no icons are shown on the bottom of the (blog) page ...

--


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-10 Thread Wayne Stambaugh 
I was hoping the icon would draw user's attention to the warning to the
obvious backup your files statement but maybe I was being a bit
optimistic.  I'm fine with it the way it is.  I just wanted to be sure I
didn't do anything wrong.

On 11/10/2017 08:48 AM, Nick Østergaard wrote:
> The source and generated code looks correct. It just seems like we don't
> have any definition for the admonitionblock div classes for the icons in
> the CSS. I guess this is a matter of taste, on whether one likes icons
> or text. I guess icons was not implemented because we didn't use many of
> these admonition blocks at the time of devising the new site template.
> 
> 2017-11-10 14:20 GMT+01:00 Wayne Stambaugh  >:
> 
> Maybe one of our resident asciidoc experts can help me out.  I used a
> WARNING admonition in the kicad website symbol library table blog
> post[1].  I was expecting to see the warning icon per the asciidoc
> documentation[2] but I only see a "WARNING" string where I expected the
> icon.  Am I doing something wrong here[3] or do we not have our asciidoc
> generator configured to use the icons for admonitions?  Thanks in
> advance for the help.
> 
> Cheers,
> 
> Wayne
> 
> [1]: http://kicad-pcb.org/post/symbol-lib-table/
> 
> [2]: http://asciidoc.org/userguide.html#X22
> 
> [3]:
> 
> https://raw.githubusercontent.com/KiCad/kicad-website/master/content/post/symbol-lib-table.adoc
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Asciidoc question.

2017-11-10 Thread Nick Østergaard 
The source and generated code looks correct. It just seems like we don't
have any definition for the admonitionblock div classes for the icons in
the CSS. I guess this is a matter of taste, on whether one likes icons or
text. I guess icons was not implemented because we didn't use many of these
admonition blocks at the time of devising the new site template.

2017-11-10 14:20 GMT+01:00 Wayne Stambaugh :

> Maybe one of our resident asciidoc experts can help me out.  I used a
> WARNING admonition in the kicad website symbol library table blog
> post[1].  I was expecting to see the warning icon per the asciidoc
> documentation[2] but I only see a "WARNING" string where I expected the
> icon.  Am I doing something wrong here[3] or do we not have our asciidoc
> generator configured to use the icons for admonitions?  Thanks in
> advance for the help.
>
> Cheers,
>
> Wayne
>
> [1]: http://kicad-pcb.org/post/symbol-lib-table/
> [2]: http://asciidoc.org/userguide.html#X22
> [3]:
> https://raw.githubusercontent.com/KiCad/kicad-website/
> master/content/post/symbol-lib-table.adoc
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Asciidoc question.

2017-11-10 Thread Wayne Stambaugh 
Maybe one of our resident asciidoc experts can help me out.  I used a
WARNING admonition in the kicad website symbol library table blog
post[1].  I was expecting to see the warning icon per the asciidoc
documentation[2] but I only see a "WARNING" string where I expected the
icon.  Am I doing something wrong here[3] or do we not have our asciidoc
generator configured to use the icons for admonitions?  Thanks in
advance for the help.

Cheers,

Wayne

[1]: http://kicad-pcb.org/post/symbol-lib-table/
[2]: http://asciidoc.org/userguide.html#X22
[3]:
https://raw.githubusercontent.com/KiCad/kicad-website/master/content/post/symbol-lib-table.adoc

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp