Re: [Kicad-doc-devs] Doc for action menu/plugins

Hi Jean-Samuel, the patch you made is made in a ... bad way. Please commit your change locally and use git format-patch such that I can apply it easily with git am. And since the docs are on github, you can also just make a pull request there if you like. Could you please do either of those

Re: [Kicad-doc-devs] Translation workflow, switch to central generated POT files?

Remember that the update-po-files.sh script has an option to not delete the POT file. I am not too concerned on what way you want to do it. I would just like to make it easy for the translators. If it takes that the POT file is always up to date, we can start doing that. 2016-08-25 7:25

Re: [Kicad-doc-devs] [PATCH] KiCadDocumentation.cmake: fix install target for HTML docu

OK, so this was where the inline email went. Discussing in [Kicad-doc-devs] [PATCH] Decrease the duplicated image data for HTML documentation 2016-09-24 18:32 GMT+02:00 Carsten Schoenert : > Hello Wayne, > > Am 24.09.2016 um 18:19 schrieb Wayne Stambaugh: >> I'm going to

Re: [Kicad-doc-devs] Please don't edit *.po files after *.adoc modification (the hard way)

Den 31/10/2016 11.02 skrev "Carsten Schoenert" : > > I was on some business trips and also on some free days of work, so I > answer with some days of delay. > > On 17.10.2016 10:19, Marco Ciampa wrote: > [...] > >>> After this I will write you to suggest a tool that could

Re: [Kicad-doc-devs] Call for the translation for 4.0.5

t can try to do a best effort and help each other reach a common goal, that is improve KiCad, respect each other, and be proud of it. :) > Best regards, > > Kinichiro > Thanks to all involved parties, and I hope you will still consider contributing in the future and remember to also use

Re: [Kicad-doc-devs] Translation work announcement ?

If the fixes are spelling fixes or code example changes, I think the text can be updated in the po files also. 2016-12-12 15:18 GMT+01:00 kinichiro inoguchi : > Hi, > > May I send the "Call for the 4.0.5 translation work" to this ML > after this Pull-Request is

Re: [Kicad-doc-devs] Translation work announcement ?

y can work for their languages or not. > - For the .po file that no translators raise hand, I will edit that. > > I'm not sure all the translators subscribing this ML, I would like to > create the 4.0.5 translation work issue on GitHub, too. > > Kinichiro > > > 201

Re: [Kicad-doc-devs] [Kicad-developers] string change proposal

2018-02-08 <20%2018%2002%2008> 6:53 GMT+01:00 Carsten Schoenert < c.schoen...@t-online.de>: > Hi, > > Am 08.02.2018 um 01:06 schrieb Nick Østergaard: > > I also thinks that adding "by Kicad" does not add any information. It > > only complicates the al

[Kicad-doc-devs] Fwd: [Kicad-developers] rc2 last call

FYI -- Forwarded message -- From: Wayne Stambaugh Date: 2018-04-22 22:37 GMT+02:00 Subject: [Kicad-developers] rc2 last call To: KiCad Developers I think we are ready to tag rc2. I'm giving everyone another day or

Re: [Kicad-doc-devs] new doc page ... and the translations...?

What do you mean by there being no links? There is a menu to select language. FWIW the master branch is not yet automatically added, so far it is only the old tagged docs. On Thu, 24 Jan 2019 at 17:58, Marco Ciampa wrote: > There are no links to the tranlated docs... > >

Re: [Kicad-doc-devs] new doc page ... and the translations...?

No worries. Yes, that is the intention. I am not sure about you, but I have heard that Rome was not built in one day. It was built during the night. -- And that is where I sleep :P fre. 25. jan. 2019 00.56 skrev Marco Ciampa : > > On Thu, Jan 24, 2019 at 11:17:34PM +0100, Nick Østergaard

Re: [Kicad-doc-devs] [Kicad-developers] 5.1 release

Forwarding to kicad-doc-devs in case anyone missed it, and adding tag intent on kicad-i18n and kicad-doc as: https://github.com/KiCad/kicad-i18n/issues/363 https://github.com/KiCad/kicad-doc/issues/691 On Fri, 8 Mar 2019 at 20:16, Wayne Stambaugh wrote: > The 5.1.0 release has been tagged and

Re: [Kicad-doc-devs] No Flags under Settings Language

Flags were removed in later versions of kicad because they are ambigious. On Fri, 22 Mar 2019 at 15:02, Alfrede wrote: > Hi together, > > in the Moment i rewrite the gui_translation_howto Documentation for German. > > Where i struggle was when i came to the Point: > > > As you see in this

Re: [Kicad-doc-devs] Documentation links

Hello Mathias, Welcome to the club. ;) This particular issue should be addressed in https://github.com/KiCad/kicad-doc-website/issues/13 Nick søn. 10. feb. 2019 11.59 skrev Alfrede : > Hi all, > > first of all i wanna say thank you for adding me in the mailinglist. > > I want to help you in

Re: [Kicad-doc-devs] Joining the doc team

The one named "kicad-services" is NOT an official kicad repo, that is someone else. Everything official about kicad on gitlab is on the "kicad" namespace. On Mon, 6 Jan 2020 at 16:37, Marco Ciampa wrote: > > On Mon, Jan 06, 2020 at 02:42:36PM +0100, f.dos.san...@free.fr wrote: > > Hi KiCad doc

Re: [Kicad-doc-devs] Documentation workflow with stable and development branch

v6 behavior and this one should > never be cherry-pick If that works for now, please do that. If you have changes that applies to 5.1, don't hold them back. It is better to get it in ASAP, if it is easy (cherry-pick'able). > > Francisco > > - Mail original - >

Re: [Kicad-doc-devs] what does this means?

u are used to. On Wed, 6 May 2020 at 10:22, Marco Ciampa wrote: > > On Wed, May 06, 2020 at 07:48:06AM +0200, Nick Østergaard wrote: > > Maybe a repo config error, I will check the permissions for you. But you > > should be able to push to your own fork an make a MR. > &g

Re: [Kicad-doc-devs] what does this means?

Maybe a repo config error, I will check the permissions for you. But you should be able to push to your own fork an make a MR. ons. 6. maj 2020 01.22 skrev Marco Ciampa : > I tried a push ... this error... > > remote: GitLab: You are not allowed to push code to protected branches on > this

Re: [Kicad-doc-devs] Documentation workflow with stable and development branch

Hi Francisco Thank you for your interest and effort. I have added you now, you should be able to manage the issuetracker, please test it. Some thoughts about yours: Tracking things to be updated or changed is better done in the issue tracker. I think all effort should be focused on the master

Re: [Kicad-doc-devs] let's be brave and fork!

to branch from 5.1.2 or 814321ecf474f2c1a6061a01122c9b3148b17a2e. I have pushed the 5.1 branch I have with merge-base on the latest commit for now. Regards Nick Østergaard On Thu, 7 May 2020 at 19:19, Jon Evans wrote: > > Why not just not translate the master docs branch (if you start

Re: [Kicad-doc-devs] Translations Locations

I don't really see it as an advantage as such to move it into the kicad source. Why do we technically need that to use weblate? On Sat, 17 Oct 2020 at 19:31, Steven A. Falco wrote: > I have no objections. It makes sense to combine those repos. > > Steve > > On 10/17/20 11:08 AM, Seth

Re: [Kicad-doc-devs] Translations Locations

t? > > Seth > > On Sat, Oct 17, 2020, 11:02 AM Nick Østergaard wrote: > >> I don't really see it as an advantage as such to move it into the kicad >> source. Why do we technically need that to use weblate? >> >> On Sat, 17 Oct 2020 at 19:31, Steven A.

Re: [Kicad-doc-devs] Problem building docs on Windows

I don't think anyone really tested it on windows before. There are probably some subtle issues. Sort of related is the wish to ditch asciidoc in favor of asciidoctor only. https://gitlab.com/kicad/services/kicad-doc/-/issues/638 On Sun, 14 Feb 2021 at 15:52, Jon Evans wrote: > > Anyone have

Re: [Kicad-doc-devs] Vacation

Thank you, enjoy your vacation. :) Den tor. 16. aug. 2018 kl. 09.26 skrev Marco Ciampa : > > Saturday 18 morning I'll be leaving for vacation until sunday 26, this > time without any laptop. > > To the admins: please keep an eye on the translations and docs pull > requests. > > To the translators

Re: [Kicad-doc-devs] created branches for kicad i18n 5.0 and 5.1

Hi I think having a one to one mapping with branches for the i18n repo is fine, and the i18n is highly dependent on the kicad src. But for the doc repo, I don't think that is needed, it is better to have as few branches here as possible, as the docs are only a meta description of kicad and not

Re: [Kicad-doc-devs] created branches for kicad i18n 5.0 and 5.1

Den ons. 18. jul. 2018 kl. 19.50 skrev Carsten Schoenert : > > Hi, > > Am 18.07.18 um 15:00 schrieb Marco Ciampa: > >> wouldn't it have been better to pull first all outstanding pull request > >> that are for the version 5.0.0 nonetheless? > > > > Whenever I see a pull request that should be

Re: [Kicad-doc-devs] User documentation build server.

The docs are not hosted there it is on http://docs.kicad-pcb.org/master/ The dev docs are also still there. ons. 11. jul. 2018 19.11 skrev Wayne Stambaugh : > I just went to http://darine.hogyros.de:8080/job/any-kicad-doc-head/ and > I cannot load the web page. I wanted to take a look at my

Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go

I don't see an advantage of creating a 5.0 branch before more issues are fixed https://github.com/KiCad/kicad-doc/issues We don't gain anything by having a 5.0 branch other than wasting valuable time. IMHO. On Thu, 11 Oct 2018 at 08:13, Marco Ciampa wrote: > > On Wed, Oct 10, 2018 at 07:04:16PM

Re: [Kicad-doc-devs] Missing SSL on kicad-pcb.org website

Using chrome 69.0.3497.100, I can still browse the page without issues. This is currently the latest release of chrome. Where is this described? I mean, that chrome will refuse to load http pages? Proper support for proper https will happen in the future, but not tomorrow. man. 24. sep. 2018

Re: [Kicad-doc-devs] Problems to build (Polish/Japanese EEschema) documentation since commit a5002028

I never got the time to try to review it, I was sort of hoping you ro report that there were no issues with. I assume you are still using it for your debian package and that it does fix the issue. Thank you for the bump. lør. 20. apr. 2019 09.00 skrev Carsten Schoenert : > Ping! > > Anyone

Re: [Kicad-doc-devs] Kicad Documentation generally

Hello Alfrede See inline comments. On Wed, 26 Jun 2019 at 19:57, Alfrede wrote: > > Hi Translaters, > > i want to translate some stuff for the German Community. Today i tell > Nick that the README had a failure on it. >

Re: [Kicad-doc-devs] vacation

Enjoy. On Mon, 22 Apr 2019 at 23:04, Marco Ciampa wrote: > Just a heads-up > I'll be abroad for a vacation for a week. > No computer, no email. > > Best regards, > > -- > > > Marco Ciampa > > > -- > Mailing list: https://launchpad.net/~kicad-doc-devs > Post to :