Re: [Kicad-developers] small typos (missing spaces)
Guys > #: pcbnew/exporters/export_hyperlynx.cpp:190 > > m_reporter->Report( > _( "File contains pad shapes that are not supported by the" > "Hyperlynx exporter (oval, rectangle, circle). They have been" > "exported as oval pads." ), > REPORTER::RPT_WARNING ); Is there no contradiction here or poor wording? The first sentence says that oval, rectangular or circular are *not* supported - as I understand. But finally these are still exported as ovals, which are... after all, unsupported. Maybe: "File contains pad shapes that are not supported by the" "Hyperlynx exporter. Only oval, rectangle, circle are allowed." "During export, they will be changed to ovals." Cheers Kerusey ___ 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] small typos (missing spaces)
> > My bad, please send me the patch with the wording you > prefer. But didn't you notice this message is not > (yet) printed anywhere as the m_reporter is always > null? > > Cheers, > Tom > I am just translating here... :( Kerusey ___ 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] Empty Gettext in pcbnew/menubar_pcb_editor.cpp
Non translatable empty strings encountered by poedit. 2018-08-24 20:38:25: pcbnew/menubar_pcb_editor.cpp:345: Empty msgid. wxMenu* autoplaceSubmenu = new wxMenu; AddMenuItem( autoplaceSubmenu, ID_POPUP_PCB_AUTOPLACE_OFF_BOARD_MODULES, _( "&Autoplace off-board components" ), _( "" ), KiBitmap( grid_select_axis_xpm ) // fixme: icons ); 2018-08-24 20:38:25: pcbnew/menubar_pcb_editor.cpp:349: empty msgid. AddMenuItem( autoplaceSubmenu, ID_POPUP_PCB_AUTOPLACE_SELECTED_MODULES, _( "&Autoplace selected components" ), _( "" ), KiBitmap( grid_select_axis_xpm ) // fixme: icons ); --- Kerusey Karyu ___ 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] Error updating standard Kicad footprint libraries from Github
$0.02 For Windows users this will be easy deal. Just create special option/task in KiCad installer. Kerusey Karyu ___ 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] SMT LEDs on board back side, but showing through a hole
Dick Hollenbeck on Mon, 10 Jun 2013 15:37:43 wrote: > > Do SMT LEDS light on their backside? If show, could a > person not use a normal SMT LED for this and simply put > a NPTH in the middle of the two pads? > > Thanks, > > Dick > If you look "a bit closer" to the LED chip, you will see a metal (usually copper) substrate which refuse to emitting light in that way. Adding with a ceramic base of each SMT LED this makes a solid barrier for a light, even for a reflected light. So, the answer is: No. http://www.semileds.com/system/files/SemiLEDs_EV_chip_e-catalogue.pdf Regards Kerusey Karyu ___ 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] KiCad Winbuilder for the GAL branch
FYI: I can't feel as one of the founders of GAL WinBuilder because my contribution was quite marginal. I was just a stone that started an avalanche. Regards Kerusey Karyu___ 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] Cleanup by splitting the atmel.lib library
Hello. I would like to split the atmel.lib into several smaller libraries. This would be a similar division to the families which already exists in the Microchip MCU libraries. My proposals are as follows: - atmel_avrlegacymcu.lib - where the symbols of Classic AVR family have been moved - atmel_avrtinymcu.lib - where the symbols of AVR Tiny family have been moved - atmel_avrmegamcu.lib - where the symbols of AVR Mega family have been moved - atmel_51mcu.lib - where the symbols of Atmel’s MCS-51 family have been moved - atmel_avrxmegamcu.lib - where the symbols of AVR Xmega family have been moved Later this same method can be used to create specific libraries for other processors families, like: SAM3, SAM4, SAMD20 (new Atmel’s Cortex M0+ devices), UC32 or many other non-MCU devices: memories, touch sensors, RF, etc. After the library split, atmel.lib could be removed to avoid duplicates. However, backward compatibility problems may face in the way in the existing users projects. (I can already see the tons of messages “Where is my library?” on the user mailing list.) Since this is a big change and may have some sort of influences, first I would like to know the opinion of developers and eventual acceptance/permission of those changes. Including the removal of atmel.lib. Regards Kerusey Karyu ___ 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] New icons for KiCAD
> Hi all! > > I want to present to you new icon set for KiCAD. > (...) > Regards, Konstantin. Gosh! I just started updating Polish help files because Fabrizio updated a couple weeks ago full icon set and I pushed a few minutes ago three modified files, and there are *brand new set*. At this rate of changes in icon sets I can not keep up on the updates. Slow down guys, please! :D Regards Kerusey Karyu ___ 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] KiCad git-based libraries as a way to harvest users' contributions - does it work?
"Does it work?" When Git library repository - I mean symbols, this is my only point of interest - was started few months ago there is one master branch, and four (If I'm wrong, sb corect me) registered contributors. Now we have eight and few people who have their own forks based on master branch. Using Git search engine and searching for "kicad", system said: "We've found 312 repository results". Even if we filter out current pretty repos we still have got about two hundred. I have look into a couple of it and there is something interesting in it which may enlarge the current libraries resource. Can we acquire these people? Or unique symbols/footprints which they done? I think yes. So, the answer for: "Does it work?" is "It works". Partially it works. But there is one thing that must be done as soon as possible, before users throw on the creation of libraries. Clear and understandable by everyone library creating policy. Actually "we" don't have it, and symbols have different styles: various pin length (Is there any reason to keep 0.3" as default value?), various text size, sometimes disproportionation symbol body size. Awful (IMHO). From a drawing point of view, footprints looks better because there is no room to any extravagance. The only unclear thing is footprint naming convention. SOT-23 or SOT23, SO8 or SO-8 or SOIC8 or SOIC-8-N. Opinions are divided, and the discussion on library-committers list was stuck in place. ps. Sorry people, but I have to put my 5 cents in this discussion. Kerusey Karyu ___ 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] [Kicad-lib-committers] Remarks to KiCad Library Convention
From: Lorenzo Marcantonio Date: Fri, 16 May 2014 12:11:25 +0200 > > So special remarks like EBC or GSD should be omitted. To seldom in > > use. > > I think the opposite is true unless in schematic you call the pins > 123. And then good luck with reversed or permuted packages. > Permuted packages? No problem. Create as many symbols as needed to match *one* stable footprint with *one* stable pinning. I prepare my libraries to use this system. When I'm placing component on schematic I don't care about footprint and his pin variation because it's hard-coded in symbol, and I'm sure that when I'm select "SOT-23" it will be fit at 100%. There is no cost to create symbols and huge amount of aliases if needed. > Also while > routing is quite useful to see that a pin is a gate instead of of, > say, just pin 1. > If you design something you know your circuit and used components. So you will be know where your gate is. Even if you're a contractor PCB designer then you got an experience to recognize the circuit or simply ask for full schematic. > it's just easier to duplicate the package and > rename the pins :D > It's easiest to create proper symbols. :P > Then you have the diodes. Good luck with them. Single diode, common > anode, common cathode and series. Sometimes the Zeners have a > different layout than the vanilla diode (rare). > Same as above. > Given this, forget the idea of the perfect library:D > It's only a matter of time and desires. > > De morgan is seldom used here, because there are no more big logical > > gates boards around anymore. Only one or to logical ICs besides the > > controllers, and there is no need for demorgan. > > Demorgan was never used anyway AFAIK, since if you can't do it on the > spot you need to change line of work anyway. But it was there on OrCAD > 1.0, so maybe is a relic of the past. > IMHO if some day KiCad receive ability to generate EDIF files this feature will be useful. Sometimes it is easiest to draw your ideas using gates instead of writing it using HDL. BTW: It would be fantastic if discussion about libraries do not split over here and there. :( Kerusey Karyu ___ 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] Announcement - Decision needed
All the Polish help docs has been ported/converted to HTML format and committed. Now you have to decide to keep, archive or remove their PDF editions and ODF sources. By the way. My friend ask me: "Why don't you use a Compiled HTML Help (CHM) system? I saw a Linux client for that..." As a "bonus track" you can take a look at English KiCad Manager doc using my style sheet. https://github.com/keruseykaryu/kicad-kerusey-doc-html/tree/master/doc/help/en Regards Kerusey Karyu ___ 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] Announcement - Decision needed
W dniu 20.09.2014 o 18:57, jp charras pisze: By the way. My friend ask me: "Why don't you use a Compiled HTML Help (CHM) system? I saw a Linux client for that..." They are binary files, and we want to remove binary files from the Launchpad repos. *All* platforms have html viewer, and not a chm viewer. Why to search problems? the only one advantage is (perhaps) a chm document is only one file instead of many files in html format, but this is a minor advantage for us. This is understandable. In addition, I can say that you can keep HTML source files and a project file for CHM and compile it on the fly. I do not know if there are compilers in systems other than Windows. Ok. I consider this subject as closed. As a "bonus track" you can take a look at English KiCad Manager doc using my style sheet. https://github.com/keruseykaryu/kicad-kerusey-doc-html/tree/master/doc/help/en Looks very good. May I ask you how you have created/exported these html files? To keep HTML clean as possible, I chose the more difficult path. The text has been transferred by "leading technology Ctrl-C/Ctrl-V" :) and every HTML tag have been added manually using only the Notepad++ editor. The graphics have been extracted from ODF files. Then, just create a CSS file to stylize it somehow. It took two weeks, but it paid off. Shorter files and only basic tags. Kerusey Karyu ___ 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] BZR2825 translation - Something is broken?
Hi everyone. I tried to update Polish kicad.po source file for the latest revision BZR2825, but during the string update process an error pops up. The log: | 19:13:36: xgettext: Non-ASCII string at | pcbnew/dialogs/dialog_copper_zones_base.cpp:192. | 19:13:36: Please specify the source encoding through | --from-code. | 19:13:36: Entries in the catalog are probably incorrect. | 19:13:36: Updating the catalog failed. Click on 'More>>' for details. The error pops up in both Poedit 1.4.6 on Windows (7HP, x86) as in Poedit 1.4.2 under Ubuntu 10.10 running on a virtual machine. So far I did not need to change any parameters on the command line to update the database as suggested in the log. :7 I have checked also indicated source file and that line just does not have strings for gettext...??? Someone has already tried to update the database of strings for your language and it is gone smoothly? Regards Kerusey Karyu (a pseudo) ___ 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] KiCad Windows builder
Dnia 2011-07-28, czw o godzinie 20:32 +0100, Brian Sidebotham pisze: > Hi Guys, > > I thought after a bit of initial testing, I might as well let this > script out in the open. I registered a launchpad project for it - > kicad-winbuilder so that people can moan and complain about the script > over there! ;-) > > The script can be grabbed via: bzr branch lp:kicad-winbuilder > > Then KiCad can be built with: cmake -P KiCadWinbuilder.cmake > > I'll email a link to it on the KiCad users group too and see how it goes. > > Best Regards, > > Brian. > Fine. But this script do nothing, because there is no "mingw-get-0.2-alpha-3" directory at http://sourceforge.net/projects/mingw/files/Automated%20MinGW% 20Installer/mingw-get :( Script produce some errors about broken archive, then go on, and finish without any action. Tested on fresh WinXP HE (SP3 PL) installed as VM in VirutalBOX. cmake and bzr installed before. --- Regards Kerusey Karyu ___ 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] KiCad Windows builder
Dnia 2011-08-01, pon o godzinie 21:53 +0100, Brian Sidebotham pisze: > On 1 August 2011 09:52, Brian Sidebotham wrote: > > On 31 July 2011 09:05, Kerusey Karyu wrote: > >> Brian, take a look at the shell screenshot and logs. Something is wrong > >> with wxWidgets section. > > Hi Kerusey, > > I have just fixed the wxWidgets build problem, and also the > out-of-date MinGW installer URL. Hopefully the MinGW installer will > become stable soon. > Well. The script is now working. :) MinGW was installed, wxWidgets are build, Kicad binaries also. But... After a 2 hours of script progress: 1) Kicad binaries are hudge. eeschema.exe is an ~10MB file for example. 2) Kicad binaries searching for libstdc++-6.dll and libgcc_s_dw2-1.dll I have found it on SF, but I think something (wx or Kicad) need a patch for easy Windows build. 3) With these dll's Kicad binaries need a long time to run. eeschema.exe for example need a 25 sec to start and show working area! Task manager shows 50% CPU usage during this time; and regular, an incremental memory "eating" up to 22 megs. :( So. I'm Looking for solution, and I need to try step by step procedure found on Yahoo groups. That's all from My own battlefield now. --- Regards Kerusey Karyu ___ 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] KiCad Windows builder
Dnia 2011-08-03, śro o godzinie 21:23 -0500, Dick Hollenbeck pisze: > Kerusey, > > The 2 hours is a function of many environment considerations. > Internet speed, > harddrive speed, computer speed are chief among them. > > There will probably be folks for which this script runs much faster > than 2 > hours, just guessing. > > (My machine compiles the entire Kicad source in 3 mins 30 seconds, on > Ubuntu > x86_64, no wxWidgets, just Kicad.) > > Dick The compilation time is not a problem. The problem is the result now. Kerusey ___ 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] [PATH] kicad app icons spacing + better icons + kicad left tree spacing
Dnia 2011-09-12, pon o godzinie 18:44 +0200, jean-pierre charras pisze: > In Eeschema, the icon used for annotation tool is not self > explanatory. > Can you create a better icon ( like the netlist icon for instance) ? > The icon used to add an image in Eeschema is not good (I am not clever > to do icons). > Can you create a better icon ? > > Thanks. > > -- > Jean-Pierre CHARRAS I agree with Jean-Pierre, that annonation tool icon is a bit questionable. But I would have one more suggestion for that section. Icon for the BOM tool (currently a wrench+screwdriver) is not fairly intuitive too. My proposal is a paper with the building blocks in the lower right corner. Kerusey Karyu ___ 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] [PATH] 50 svg icons re-drawn and improved
Dnia 2011-09-13, wto o godzinie 14:58 +0200, fabrizio pisze: > in attachment you can find a zipped folder new_kicad_svg.zip that > contains 50 re-drawn .svg icons that are better drawn according to all > the suggestions received. I do not think you should change the EEschema icons for libraries tools in this way. The current icons are excellent. With minor modifications, they would meet My personal criteria. :P For the library creating tool you can put a pencil over a notebook (taken from current annonation tool icon, but smaller) and for library browsing tool a magnifying glass on the corner. I think the standard and worldwide understanding symbols: - an asterisk = something new - a pencil = something to write/create - a maginifier = something to view are still the best solutions. - One more think. I thought about annonation tool icon. Leave the pencil and draw the resistor symbol in the background (in the perspective shot), which this pencil markings "R1"... What do You think? Kerusey Karyu ___ 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] Trigonometric look up table.
Dnia 2011-09-19, pon o godzinie 11:15 -0400, Wayne Stambaugh pisze: > Is there any logical reason to keep using the trigonometric look up tables in > trigo.cpp? We currently have a mixed bag of using the look up tables and the > math sin() and cos() functions in various code paths. If no one objects, I > think it's time to remove them from Kicad. > > Wayne > I'm not familiar with a KiCAD source, but I think the lookup tables should stay. Why? In some cases a lookup will be faster than math functions. I don't know, but while redrawing - an arc for example - these tables speed-up a lot the screen refreshing. Kerusey Karyu ___ 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] Kicad future documentation - your opinion
Dnia 2011-09-22, czw o godzinie 17:00 +0200, fabrizio pisze: > from the repository: > lp:~kicad-developers/kicad/doc > > I notice that the polish version of kicad-doc.pdf which is : > kicad-doc/doc/help/pl/kicad.pdf > > has been already update with the new icon. That is impressive ! I > however have to point out that since the time when this doc started > being updated, some icons have changed a little (not so much). > Wow! Someone noticed the new and updated edition. Finally. :D :D Yes. Images came from a previous icon version of KiCAD, but my compilation is constantly updated (Thanks Brian!). As I'll translate the EESchema content I'll change images in cvpcb.pdf, kicad.pdf and the older ones into eeschema.pdf. Of course I've vote for YES to remain the OpenDocument format and PDF as a final result. Since we have KiCAD OpenSource, so OpenDocument is the natural choice. In a Polish version, due to the applied styles (new layout of the text), files are not linked by the ODM file. Unfortunately, everything started to fall when I've trying to join the cover sections and the text for particular headings with ODM. Hence the decision to write new Polish doc source in a single file. Kerusey Karyu ___ 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] Kicad future documentation - first draft
Dnia 2011-09-26, pon o godzinie 17:14 +0200, fabrizio pisze: > Dear All, > I seem to understand that the use of the .odt (and pdf) format and > LibreOffice as main editor is the choice preferred by most of the > people. > LibreOffice or OpenOffice. No matter. > In attachment you can find the document kicad_en.pdf modified and > updated. The following modifications where made: > - front cover was redesigned (any suggestions for improvement?) > This KiCad main icon is ugly. :( This form is good for documents, but not for the whole application. Anyway, compare it yourself with the rest of icons of the KiCad Suite members. Clearly does not fit. BTW: Why CvPCB icon has a blue base? The text is ok, but what the Cannonical says... > - A quite cool template (taken from the official open office > documentation) was used to restyle the whole doc. > - New icons and screenshots (all included as local links) > - some minor corrections > IMHO the new KiCad documentation should be a big-bang for the future readers. In general. Your layout is too "polite". Especially with these smoothing green headers. The Arial font or his equivalent - it already was. Lack of emphasis for important key words, no monotype in file paths or names - the fundamental elements of IT manuals are missing. Sorry. But I do not like it. Kerusey Karyu ___ 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] Kicad future documentation - first draft
Dnia 2011-09-27, wto o godzinie 10:30 +0200, fabrizio pisze: > # What aspect of the KiCad icon don't you like? What icon would you > have in mind? Kicad icon is currently the dominant icon because it is > not the icon of an application per se but the icon of the whole suite, > therefore I though of giving it a general non-application look. > (...) > Are we talking about the KiCad icon or the icon in the manual cover? > I see, you are a big fan of LibreOffice. I mean your icon on documentaton cover page in kicad.pdf. This graphics are very well inspired of LibreOffice logo. But. What is good for word processing software, ins't sometimes good for an EDA software suite. > Send me an .svg of what you might like. > I'm not a graphic designer. :( > # What kind of icon would you like for CvPCB? Please, if you can, send > examples. Lots of improvement can be done with this icon. > Just remove this blue background. > # What do you mean by "what the Canonical says"? > Did You remember the older logos of Ubuntu or Kubuntu? Font, reflection under text... Just compare. See where will be the problem? > # What do you mean by "Your layout is too "polite""? If you have a > look at the style available in this template you can see that there > are styles for all possible element of a manual. This template is the > template of the official libreOffice documentation and It was designed > by several people who I think know stuff. I'm not sure I can do better > than them but If you think you can please send it to me and we can ask > around for opinions. > My Kicad examples/proposal you can find in doc repository for a few weeks. Nobody said no, so I cotinue my work to create a polish one. Offical colour of LibreOffice is green. Why green should be good for KiCad too? Why LibreOffice templates should be good? Kerusey Karyu ___ 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] Time to say goodbye
Hello everybody. It's the time to end my activity on this mailing list. Today I unsubscribe from them. My Lauchpad account will be also deleted. So... Thank You and Goodbye. Kerusey Karyu ___ 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] new documentation format
To: kicad-developers From: Marco Ciampa Date: Tue, 21 Oct 2014 23:58:17 +0200 > If you have any doubt or problem about anything please > express yourself. > I consider that the use of formats to create documentation using translations in the form of translation database (.po files) will, despite the many advantages, also some disadvantages for translators. While the use of such forms of translations for the UI is quite comfortable, the use of that form for translating a continuous text (which is result of the train of thoughts) can be very uncomfortable for translators. Why? The main difficulty will be limited visibility of the logic of the text and its layout (indentation, spacing). There will be situations where we will need to translate a fragment out of context. I as a translator prefer also see more of the text to be able to, among others, eliminate repetition of words and the use of synonyms. My native language is very flexible in this topic. Taking also the specificity of translated texts, unfortunately, it is in so many cases impossible to translate word for word. Sometimes you have to break down complex sentence into two (or even three) sentences that the reader can easily assimilate them. By translating KiCad user manual I had to just do that many times. Sometimes adding something from each other to avoid ambiguity. So. That’s my (maybe wrong) doubts. Regards Kerusey Karyu ___ 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] Library Developers.
Hi everyone. Let me express few words about changes in the symbol libraries. At the moment there are no major changes in the naming of the current symbol library files. Together with GitHub users we added and we are planning to add a few new ones. One library is provided for the liquidation in near future from the current library set: 'special.lib', as it has become a kind of garbage dump (IMO). The discussion is here: https://github.com/KiCad/kicad-library/issues/153 Last year, only one library has been removed: 'microchip1.lib', as I remember. The biggest changes are taking place within the existing libraries. The establishment of strict rules written in the KiCad Library Convention document forces far-reaching changes in symbols including also those in existing libraries. Refresh the older schematics will unfortunately be *necessary*. Many existing symbols were drawn without any rules. That's why they look the way they do. We realize that such changes will be immediately negative commented and might be refused by users, but unfortunately we have no choice. Along with the improvement of the quality of KiCad as an EDA Tool we have to go to improve the quality of libraries contained therein. Best Regards Kerusey Karyu ___ 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
