That particular commit didn't, but latest is good.
lør. 9. mar. 2019 07.27 skrev Simon Richter :
> Hi,
>
> the documentation failed to compile for me last night:
>
> https://jenkins.simonrichter.eu/job/any-kicad-doc-head/569/
>
> Is that just me, or is something broken?
>
>Simon
>
> _
Hi,
the documentation failed to compile for me last night:
https://jenkins.simonrichter.eu/job/any-kicad-doc-head/569/
Is that just me, or is something broken?
Simon
signature.asc
Description: OpenPGP digital signature
___
Mailing list: http
On Wed, Jan 31, 2018 at 06:13:33PM +0100, Carsten Schoenert wrote:
> Hello Marco,
>
> Am 31.01.18 um 17:34 schrieb Marco Ciampa:
> > Here we are... see attach
>
> please follow some traditional rules for textiles, markdown isn't
> anything special, and keep the line breaks in such files between 7
I merged this patch.
2018-01-31 17:34 GMT+01:00 Marco Ciampa :
> Here we are... see attach
>
> Regards,
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
>
>
> GNU/Linux User #78271
> FSFE fellow #364
>
>
>
>
> _
Hello Marco,
Am 31.01.18 um 17:34 schrieb Marco Ciampa:
> Here we are... see attach
please follow some traditional rules for textiles, markdown isn't
anything special, and keep the line breaks in such files between 76 and
80 characters. Don't just simple write some long lines without any line
bre
Here we are... see attach
Regards,
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
GNU/Linux User #78271
FSFE fellow #364
>From 7d0f42d41faf579b74f7cc03939188031858cac7 Mon Sep 17 00:00:00 2001
From: Marco Ciampa
Date
On Wed, Jan 31, 2018 at 08:58:06AM -0500, Wayne Stambaugh wrote:
> On 1/31/2018 8:21 AM, Maciej Sumiński wrote:
> > On 01/31/2018 01:03 PM, Marco Ciampa wrote:
> >> On Wed, Jan 31, 2018 at 12:43:34PM +0100, Maciej Sumiński wrote:
> >>> On 01/31/2018 12:35 PM, Marco Ciampa wrote:
> On Wed, Jan
On 1/31/2018 8:21 AM, Maciej Sumiński wrote:
> On 01/31/2018 01:03 PM, Marco Ciampa wrote:
>> On Wed, Jan 31, 2018 at 12:43:34PM +0100, Maciej Sumiński wrote:
>>> On 01/31/2018 12:35 PM, Marco Ciampa wrote:
On Wed, Jan 31, 2018 at 12:16:50PM +0100, Maciej Sumiński wrote:
> Does anyone curr
On 01/31/2018 01:03 PM, Marco Ciampa wrote:
> On Wed, Jan 31, 2018 at 12:43:34PM +0100, Maciej Sumiński wrote:
>> On 01/31/2018 12:35 PM, Marco Ciampa wrote:
>>> On Wed, Jan 31, 2018 at 12:16:50PM +0100, Maciej Sumiński wrote:
Does anyone currently work on the user documentation updates? I pla
On Wed, Jan 31, 2018 at 12:43:34PM +0100, Maciej Sumiński wrote:
> On 01/31/2018 12:35 PM, Marco Ciampa wrote:
> > On Wed, Jan 31, 2018 at 12:16:50PM +0100, Maciej Sumiński wrote:
> >> Does anyone currently work on the user documentation updates? I plan to
> >> do so, but I would rather avoid work
On 01/31/2018 12:35 PM, Marco Ciampa wrote:
> On Wed, Jan 31, 2018 at 12:16:50PM +0100, Maciej Sumiński wrote:
>> Does anyone currently work on the user documentation updates? I plan to
>> do so, but I would rather avoid work duplication.
>>
>> Regards,
>> Orson
>
> Great, if you do it, a big THAN
On Wed, Jan 31, 2018 at 12:16:50PM +0100, Maciej Sumiński wrote:
> Does anyone currently work on the user documentation updates? I plan to
> do so, but I would rather avoid work duplication.
>
> Regards,
> Orson
Great, if you do it, a big THANK YOU!
Docs really need a revise, especially screensho
Does anyone currently work on the user documentation updates? I plan to
do so, but I would rather avoid work duplication.
Regards,
Orson
signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Pos
Please delete:
Documentation/GUI_Translation_HOWTO.odt
Documentation/GUI_Translation_HOWTO.pdf
since now the reference source is in the kicad-doc repo now.
Regards,
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/Linux User #78271 |
| FSF
We're sneaking up on it. I prefer the slow steady progression. Yes,
most folks would love to everything done right now. All that does is
burn people out so you have these big changes in a short period of time
and then nothing for long periods of time.
On 8/21/2015 9:03 AM, Adam Wolf wrote:
> Ev
Everyday things get a little bit better. Good work team!
On Aug 21, 2015 8:02 AM, "Wayne Stambaugh" wrote:
> Just a heads up for all of our documentation developers. I've deleted
> the kicad-doc branch from KiCad project on github and sent an invitation
> to Marco so he can transfer the master
Just a heads up for all of our documentation developers. I've deleted
the kicad-doc branch from KiCad project on github and sent an invitation
to Marco so he can transfer the master copy of kicad-doc to the KiCad
project. Please do not send any pull requests to Marco's kicad-doc repo
until after
> On Jul 26, 2015, at 2:08 AM, Marco Ciampa wrote:
>
> Coming home after long due holydays, I see this:
>
> On Mon, Jul 06, 2015 at 08:37:24AM -0700, Andy Peters wrote:
>> I am glad to help out with docs. If someone would be so kind as to
>> point me in the right direction, I’ll do what I can.
Just tested the output of the Nick CI
http://ci.kicad-pcb.org/job/kicad-doc-with-cmake/ws/
Very good! Congrats to Brian and to Nick for the quick CI build!
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/Linux User #78271 |
| FSFE fellow
Thanks Nick, now fixed.
Best Regards,
Brian.
On 11 April 2015 at 08:56, Nick Østergaard wrote:
> 2015-04-11 9:54 GMT+02:00 Nick Østergaard :
>> 2015-04-11 1:10 GMT+02:00 Brian Sidebotham :
>>> On 8 April 2015 at 14:08, Wayne Stambaugh wrote:
On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
>>
2015-04-11 9:54 GMT+02:00 Nick Østergaard :
> 2015-04-11 1:10 GMT+02:00 Brian Sidebotham :
>> On 8 April 2015 at 14:08, Wayne Stambaugh wrote:
>>> On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
> Now that we are in feature freeze, I need an
2015-04-11 1:10 GMT+02:00 Brian Sidebotham :
> On 8 April 2015 at 14:08, Wayne Stambaugh wrote:
>> On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
>>> On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
Now that we are in feature freeze, I need an update on where we stand as
far as the asciid
On 8 April 2015 at 14:08, Wayne Stambaugh wrote:
> On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
>> On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
>>> Now that we are in feature freeze, I need an update on where we stand as
>>> far as the asciidoc documentation conversion process is concerned.
On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
> On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
>> Now that we are in feature freeze, I need an update on where we stand as
>> far as the asciidoc documentation conversion process is concerned. I
>> did a git pull yesterday and now `make html` fails
2015-04-08 10:51 GMT+02:00 Brian Sidebotham :
> On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
>> Now that we are in feature freeze, I need an update on where we stand as
>> far as the asciidoc documentation conversion process is concerned. I
>> did a git pull yesterday and now `make html` fail
On 4 April 2015 at 16:23, Wayne Stambaugh wrote:
> Now that we are in feature freeze, I need an update on where we stand as
> far as the asciidoc documentation conversion process is concerned. I
> did a git pull yesterday and now `make html` fails for a missing po
> directory. I have a few quest
Den 06/04/2015 22.53 skrev "Wayne Stambaugh" :
>
> On 4/6/2015 2:16 PM, jp charras wrote:
> > Le 06/04/2015 19:55, Wayne Stambaugh a écrit :
> >> One other important note. I just noticed that the legacy odt kicad-doc
> >> repo on launchpad has commits up to 4/5 (yesterday). All of the doc
> >> de
On 4/6/2015 2:16 PM, jp charras wrote:
> Le 06/04/2015 19:55, Wayne Stambaugh a écrit :
>> One other important note. I just noticed that the legacy odt kicad-doc
>> repo on launchpad has commits up to 4/5 (yesterday). All of the doc
>> devs need to stop using this repo or you changes could get lo
Le 06/04/2015 19:55, Wayne Stambaugh a écrit :
> One other important note. I just noticed that the legacy odt kicad-doc
> repo on launchpad has commits up to 4/5 (yesterday). All of the doc
> devs need to stop using this repo or you changes could get lost. The
> asciidoc documentation is now the
One other important note. I just noticed that the legacy odt kicad-doc
repo on launchpad has commits up to 4/5 (yesterday). All of the doc
devs need to stop using this repo or you changes could get lost. The
asciidoc documentation is now the official documentation for the project
so please contr
2015-04-06 16:54 GMT+02:00 Marco Ciampa :
> I have decided to "open" my documentation repository more, to
> encourage/foster the development of the documentation migration
> effort.
>
> Due to the nature of the CVSs, where every error could be easily
> reversed, that should not come up to any real
I have decided to "open" my documentation repository more, to
encourage/foster the development of the documentation migration
effort.
Due to the nature of the CVSs, where every error could be easily
reversed, that should not come up to any real problem.
Having said this, I have promoted as "colla
Ok))
04.04.2015 21:54, Marco Ciampa пишет:
Just to make the whole thing clear(er).
The way it is done now, the method used to handle the documents
compilation, permit to separate the Author from the Translator in a way
that the Author can work on the docs freely. The Translator's life is
really
Just to make the whole thing clear(er).
The way it is done now, the method used to handle the documents
compilation, permit to separate the Author from the Translator in a way
that the Author can work on the docs freely. The Translator's life is
really easier because the system handle the work-in-
On Sat, Apr 04, 2015 at 08:06:14PM +0300, Eldar Khayrullin wrote:
> Maybe I can mistaken, but I think that need to divide each i18n to
> separate repos on Github in accordance
> them language, for example kicad-doc-ru, kicad-doc-fr and so on.
> Each repo contains two languages one from them
> engli
On Sat, Apr 04, 2015 at 05:35:23PM +0200, Nick Østergaard wrote:
> 2015-04-04 17:23 GMT+02:00 Wayne Stambaugh :
> > Now that we are in feature freeze, I need an update on where we stand as
> > far as the asciidoc documentation conversion process is concerned. I
> > did a git pull yesterday and now
Maybe I can mistaken, but I think that need to divide each i18n to
separate repos on Github in accordance
them language, for example kicad-doc-ru, kicad-doc-fr and so on. Each
repo contains two languages one from them
english. kicad-doc-en main repo contains only english language. Other
repos pu
2015-04-04 17:23 GMT+02:00 Wayne Stambaugh :
> Now that we are in feature freeze, I need an update on where we stand as
> far as the asciidoc documentation conversion process is concerned. I
> did a git pull yesterday and now `make html` fails for a missing po
> directory. I have a few questions
Now that we are in feature freeze, I need an update on where we stand as
far as the asciidoc documentation conversion process is concerned. I
did a git pull yesterday and now `make html` fails for a missing po
directory. I have a few questions about the current state of the
documentation.
1) Is
On 9 February 2015 at 12:46, Brian Sidebotham
wrote:
> I didn't see an /official/ announcement so I wanted to just put it out
> there clearly, that AsciiDoc is the chosen format for KiCad's
> documentation (user manuals and the like).
>
> More information about asciidoc can be is available from th
I didn't see an /official/ announcement so I wanted to just put it out
there clearly, that AsciiDoc is the chosen format for KiCad's
documentation (user manuals and the like).
More information about asciidoc can be is available from the asciidoc
homepage: http://www.methods.co.nz/asciidoc/
..and
On Fri, Feb 06, 2015 at 11:55:58AM +1300, Blair Bonnett wrote:
> On 6 February 2015 at 02:52, Wayne Stambaugh wrote:
> >
> > Marco, you may want to enlist some help. Once all of the documentation
> > and build configuration is ready to go, I expect that there will be a
> > lot of pull requests to
On 6 February 2015 at 02:52, Wayne Stambaugh wrote:
>
> Marco, you may want to enlist some help. Once all of the documentation
> and build configuration is ready to go, I expect that there will be a
> lot of pull requests to get the documentation ready for the stable
release.
>
Some form of task
On Wed, Feb 04, 2015 at 01:31:25AM +, John Beard wrote:
[...]
Well, I could not have said it better.
We can choose a format now, knowing that eventually it will not be so
difficult to change again into another format in the future if we decide
to do so.
And if I have done some work I have to
On 2/5/2015 9:45 AM, Fat-Zer wrote:
> 2015-02-05 16:52 GMT+03:00 Wayne Stambaugh :
>> On 2/5/2015 5:03 AM, Fat-Zer wrote:
>>> 2015-02-04 19:52 GMT+03:00 Wayne Stambaugh :
CMake should be used as the build configuration tool which is used to
verify all of the required tools are instal
2015-02-05 16:52 GMT+03:00 Wayne Stambaugh :
> On 2/5/2015 5:03 AM, Fat-Zer wrote:
>> 2015-02-04 19:52 GMT+03:00 Wayne Stambaugh :
>>>
>>> CMake should be used as the build configuration tool which is used to
>>> verify all of the required tools are installed on the system and
>>> automatically gen
On 2/5/2015 5:03 AM, Fat-Zer wrote:
> 2015-02-04 19:52 GMT+03:00 Wayne Stambaugh :
>>
>> CMake should be used as the build configuration tool which is used to
>> verify all of the required tools are installed on the system and
>> automatically generate the appropriate Makefiles. CMake files would g
On 5 February 2015 at 10:54, Miguel Ángel Ajo wrote:
> https://github.com/Fat-Zer/kicad-doc/tree/cmake
>
> It’s in a separate branch :-)
>
> Miguel Ángel Ajo
Ah, I was missing something! lol.
Thanks Miguel...
Best Regards,
Brian.
___
Mailing list: h
https://github.com/Fat-Zer/kicad-doc/tree/cmake
It’s in a separate branch :-)
Miguel Ángel Ajo
On Thursday, 5 de February de 2015 at 11:53, Brian Sidebotham wrote:
> On 5 February 2015 at 10:03, Fat-Zer (mailto:fatz...@gmail.com)> wrote:
> > 2015-02-04 19:52 GMT+03:00 Wayne Stambaugh > (
On 5 February 2015 at 10:03, Fat-Zer wrote:
> 2015-02-04 19:52 GMT+03:00 Wayne Stambaugh :
>>
>> CMake should be used as the build configuration tool which is used to
>> verify all of the required tools are installed on the system and
>> automatically generate the appropriate Makefiles. CMake file
2015-02-04 19:52 GMT+03:00 Wayne Stambaugh :
>
> CMake should be used as the build configuration tool which is used to
> verify all of the required tools are installed on the system and
> automatically generate the appropriate Makefiles. CMake files would go
> in the kicad-doc repo and replace the
Sorry, I believe I understood wrong previous Nick suggestion about
hosting stuff at the current kicad servers.
I’m all for doing CI, and rendering the documentation out to:
http://doc.kicad-pcb.org or the chosen subdomain.
If that was the suggestion, that’s only static file serving, w
On 02/04/2015 10:13 AM, Nick Østergaard wrote:
I'll put a CMake build system in place on the documentation and make
>>sure it works on Windows + Linux. OSX guys will have to help me in
>>making sure it works there. It shouldn't be a problem though.
What does this cmake include? Does it reside i
On Wed, Feb 04, 2015 at 05:13:05PM +0100, Nick Østergaard wrote:
> I think HTML and PDF is what is required, I guess some people would
> like epub, but that is basically not much different to HTML in
> structure, hence I think that should look equally fine in HTML as in
> epub.
AFAIK epub is more
On Wednesday, 4 de February de 2015 at 17:52, Wayne Stambaugh wrote:
> On 2/4/2015 11:13 AM, Nick Østergaard wrote:
> > 2015-02-04 15:06 GMT+01:00 Wayne Stambaugh > (mailto:stambau...@gmail.com)>:
> > > On 2/4/2015 7:10 AM, Brian Sidebotham wrote:
> > > > On 4 February 2015 at 00:14, Wayn
On 2/4/2015 11:13 AM, Nick Østergaard wrote:
> 2015-02-04 15:06 GMT+01:00 Wayne Stambaugh :
>> On 2/4/2015 7:10 AM, Brian Sidebotham wrote:
>>> On 4 February 2015 at 00:14, Wayne Stambaugh wrote:
We need to make a decision soon if we want to get the documentation
conversion completed in
On Wednesday, 4 de February de 2015 at 15:06, Wayne Stambaugh wrote:
> - Set up repo on some git hosting sight. I heard some negative feedback
> at FOSDEM about using github since apparently it is not free software so
> I'm open to suggestion on this. If github is the best choice then I'm
> OK usin
2015-02-04 15:06 GMT+01:00 Wayne Stambaugh :
> On 2/4/2015 7:10 AM, Brian Sidebotham wrote:
>> On 4 February 2015 at 00:14, Wayne Stambaugh wrote:
>>> We need to make a decision soon if we want to get the documentation
>>> conversion completed in time for the next stable release. I'm still not
>>
On 2/4/2015 7:10 AM, Brian Sidebotham wrote:
> On 4 February 2015 at 00:14, Wayne Stambaugh wrote:
>> We need to make a decision soon if we want to get the documentation
>> conversion completed in time for the next stable release. I'm still not
>> sure we can build on Windows. Neither the MSYS2
On Wed, Feb 04, 2015 at 12:10:25PM +, Brian Sidebotham wrote:
> I think we're pretty much decided already on asciidoc - it just takes
> someone to say so. I've included Marco on this email so perhaps he
> could give us his up-to-date conclusion and we can make the decision
> now.
I'm pretty su
On 4 February 2015 at 00:14, Wayne Stambaugh wrote:
> We need to make a decision soon if we want to get the documentation
> conversion completed in time for the next stable release. I'm still not
> sure we can build on Windows. Neither the MSYS2 asciidoc or sphinx
> implementations worked correc
And with the CI build, I mean, windows builders could just fetch
documentation in rendered format from our build system, and then
just package it.
Miguel Ángel Ajo
On Wednesday, 4 de February de 2015 at 13:02, Miguel Ángel Ajo wrote:
> We currently have a CI build for the asciidocs, nickoe too
We currently have a CI build for the asciidocs, nickoe took care
of setting up the CI job.
[2] http://ci.kicad-pcb.org/job/kicad-doc-testing/ws/src/asciidoc/KiCad/
Definitely, having a docker image should make it easier to replicate,
as setting up the job required a lot of dependencies to be ma
On Wed, 2015-02-04 at 01:31 +, John Beard wrote:
> On Tue, 2015-02-03 at 19:14 -0500, Wayne Stambaugh wrote:
>
> I think the availability of tools on those platforms is actually not of
> huge significance. The worst case is that the docs are built for every
> commit by something like Jenkins,
On Tue, 2015-02-03 at 19:14 -0500, Wayne Stambaugh wrote:
> On 2/3/2015 6:55 PM, Cirilo Bernardo wrote:
> > It has been some time since Marco has done an evaluation of document
> > format alternatives. Has any decision been made yet about what format we
> > shall use, or are there still some other
We need to make a decision soon if we want to get the documentation
conversion completed in time for the next stable release. I'm still not
sure we can build on Windows. Neither the MSYS2 asciidoc or sphinx
implementations worked correctly the last time I tried them and I have
no way to test any
It has been some time since Marco has done an evaluation of document format
alternatives. Has any decision been made yet about what format we shall
use, or are there still some other alternatives which are being
investigated?
- Cirilo
___
Mailing list: h
On Thu, Feb 13, 2014 at 09:21:57AM -0800, Henner Zeller wrote:
> I am interested in the scripting support - is there some documentation
> somewhere to get me started on that ?
Plotting thru scripting can do the layering thing. The documentation is
in the mail archives :P Otherwise I could dig out
On 13 February 2014 13:11, Cirilo Bernardo wrote:
> - Original Message -
>
>> From: Henner Zeller
>> To: KiCad Developers
>> Cc:
>> Sent: Thursday, February 13, 2014 6:10 PM
>> Subject: [Kicad-developers] Documentation footprint postscript/pdfs
- Original Message -
> From: Henner Zeller
> To: KiCad Developers
> Cc:
> Sent: Thursday, February 13, 2014 6:10 PM
> Subject: [Kicad-developers] Documentation footprint postscript/pdfs in
> kicad-library are HUGE bitmap images.
>
> Hi,
> The docum
On 2/13/2014 12:36 PM, Adam Wolf wrote:
> I'll try to keep an eye out, but if the plotting scripting changes, it'd
> be great if someone could ping me. I maintain a private branch that can
> generate gerbers from the command line, and would like to push it
> upstream as soon as it is acceptable.
>
I'll try to keep an eye out, but if the plotting scripting changes, it'd be
great if someone could ping me. I maintain a private branch that can
generate gerbers from the command line, and would like to push it upstream
as soon as it is acceptable.
Adam Wolf
Wayne and Layne, LLC
On Thu, Feb 13,
On 13 February 2014 00:16, Lorenzo Marcantonio
wrote:
> On Thu, Feb 13, 2014 at 12:04:47AM -0800, Henner Zeller wrote:
>> Good. Rule of thumb: always avoid widget library printing: it always sucks
>> :-)
>
> Not necessarily... wx (among other issues) truncate(d) unnecessarily
> coordinates. People
On Feb 13, 2014 12:29 AM, "jp charras" wrote:
>
> Le 13/02/2014 08:10, Henner Zeller a écrit :
> > Hi,
> > The documentation files in
> >
https://github.com/KiCad/kicad-library/tree/master/modules/footprints_doc
> >
> > Are very huge. In fact, this directory alone contributes to 502M out
> > of 58
On Thu, Feb 13, 2014 at 12:04:47AM -0800, Henner Zeller wrote:
> Good. Rule of thumb: always avoid widget library printing: it always sucks
> :-)
Not necessarily... wx (among other issues) truncate(d) unnecessarily
coordinates. People trying to do toner-transfer PCBs weren't happy. But,
among the
Le 13/02/2014 08:10, Henner Zeller a écrit :
> Hi,
> The documentation files in
>https://github.com/KiCad/kicad-library/tree/master/modules/footprints_doc
>
> Are very huge. In fact, this directory alone contributes to 502M out
> of 580M of the whole kicad-library. Yes, almost 90% of the data
On Feb 12, 2014 11:34 PM, "Lorenzo Marcantonio"
wrote:
>
> On Wed, Feb 12, 2014 at 11:10:17PM -0800, Henner Zeller wrote:
> > parts, I have not entered the printing realm yet - what is the
> > commandline way to generate a postscript file from a *.sch or *.brd
> > file ? That way, these things can
>
> I'd like to write a Makefile that generates new, higher quality
> postscripts, easy-updatable. What would be a commandline-call to
> pcbnew to do that ?
>
I don't think Kicad and its apps has any commandline options, else it has
been introduced recently without me knowing. There was once a try
On Wed, Feb 12, 2014 at 11:10:17PM -0800, Henner Zeller wrote:
> parts, I have not entered the printing realm yet - what is the
> commandline way to generate a postscript file from a *.sch or *.brd
> file ? That way, these things can be automated in a Makefile.
Kicad self-nominated plotting driver
Hi,
The documentation files in
https://github.com/KiCad/kicad-library/tree/master/modules/footprints_doc
Are very huge. In fact, this directory alone contributes to 502M out
of 580M of the whole kicad-library. Yes, almost 90% of the data
downloaded for the kicad-library is pixelated PostScript
80 matches
Mail list logo
