giseldo/neodataset huggingface dataset:
HTML text is untranslated (lp:#1818998)

[Original report](https://bugs.launchpad.net/bugs/1818998) created by **Marco Ciampa (ciampix)**
```
In the KiCad Calculator for rf attenuators there is a formula untranslated
(and untranslatable).
That text should be translatable...
```
Original tags: eeschema pcb-calculator starter

Story points: 6.0
stripes on cu layer printout (lp:#1818971)

[Original report](https://bugs.launchpad.net/bugs/1818971) created by **THOR-00 (thor-00)**
```
when printing out cu layers as pdf then inner layer have stripes all over.
used kicad info:
Application: kicad
Version: (5.1.0-rc2-38-g4612175da), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: printing

Story points: 6.0
DRC window should not close when error is double clicked (lp:#1818965)

[Original report](https://bugs.launchpad.net/bugs/1818965) created by **Urs Obernolte (urs-obernolte)**
```
The DRC window should not close when the error is double clicked. Today its
quite normal to have 2 monitors or a big enough monitor to have both
windows on screen at the same time. It is rather annoying that you have to
open it up again and again.
```
Original tags: drc feature.request pcbnew

Story points: 6.0
Alt+O doesn't confirm in Pin Properties Dialogue Box (lp:#1818930)

[Original report](https://bugs.launchpad.net/bugs/1818930) created by **George Brown (gbrown128)**
```
While adding or editing a symbol pin in eeschema the "Pin Properties"
dialogue box is shown. Most dialogue boxes in KiCad bind Alt+O to "OK". In
this box however Alt+O binds to the orientation drop down as well as the OK
button. Consequently using that shortcut does nothing.

Not sure if there is a "style guide" of sorts for this, but it would seem
to move the orientation bind to another letter.

Thank you!

Checked this in the current nightly and the latest stable in Ubuntu 18.04,
using the PPAs.
Nightly: Version: 5.1.0-rc2-unknown-4612175~94~ubuntu18.04.1, release build
Stable: Version: 5.0.2-bee76a0~70~ubuntu18.04.1, release build
```
Original tags: eeschema ui

Story points: 6.0
eeschema: Add symbol and start library editor use same icon on button (lp:#1818928)

[Original report](https://bugs.launchpad.net/bugs/1818928) created by **Laurent Haas (efcis)**
```
Related to bug report #1818867
https://bugs.launchpad.net/kicad/+bug/1818867

eeschema also has the same icon (small op amp) for the symbol editor (top
toolbar), and the "Place symbol" tool (right toolbar).

Application: kicad
Version: (5.1.0-rc2-38-g4612175da), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema ui

Story points: 10.0
Current nightly(??) pcbnew find command  requires extra keystroke (lp:#1818906)

[Original report](https://bugs.launchpad.net/bugs/1818906) created by **BobZ18188 (bobz18188)**
```
I updated Kicad from the release build to a nightly in the middle of
working on my first board.  (bad idea?)

I report that the pcbnew "find" command now seems to require an extra
keystroke.

ALT > E > F (and at this point the previous version took me to the "find"
dialog box.  Eescheema still works that way).  But in Pcbnew with the
nightly build, hitting the "F" only highlights "Find" from the top menu,
and I have to now hit "enter" in order to get the "find" dialog box.
Perhaps this is intentional or perhaps not......

++++++++++++++++++++++++++++++++++++++++++++++++++++++

Application: kicad
Version: (5.1.0-rc2-38-g4612175da), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0
Show filter effects in cvpcb (lp:#1818888)

[Original report](https://bugs.launchpad.net/bugs/1818888) created by **Simon Richter (sjr)**
```
It would be nice to see somewhere in cvpcb how many matches were removed by
filters.

This would be most useful if no matches remain, so a possible
implementation would show a summary instead of an empty list:

    No matches.

    13 footprints available in other libraries [Disable Library Filter]
    200 footprints available with different pin count [Disable Pin Count
Filter]

A small status line that is always shown would be nice as well, so we can
get a quick preview of what will happen when we enable or disable filters.
```
Original tags: eeschema

Story points: 8.0
eeschema - assign footprints - no individual delete button/option (lp:#1818883)

[Original report](https://bugs.launchpad.net/bugs/1818883) created by **ocb-hd-ccb (ocb-hd-ccb)**
```
There is no way to individually delete an assigned footprint from 'eeschema
- assign footprints'.

I tried to remove some assigned footprints after realizing I wanted to
change the package size of the component but haven't picked a replacement
yet. Being able to remove the currently assigned footprint would allow me
to know that it was still needing to be done. I temporally fixed my issue
by going into 'eeschem - symbol properties' and deleting the assigned
footprint. This did work but I had to do it for each of the 10 resistors
and 10 caps I decided to update.

Application: kicad
Version: (5.1.0-rc2-9-g37962b717), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.4 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.2.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002
Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema ui

Story points: 6.0
Pcbnew crashes when using + or - hotkeys for zoom (lp:#1818868)

[Original report](https://bugs.launchpad.net/bugs/1818868) created by **BobZ18188 (bobz18188)**
```
I thought I reported this bug yesterday but cannot see it.  I don't think
it got into your system.

I have used ExpressPCB for many years.  It uses + and - as zoom hotkeys, so
I chose the same for KiCad.  They work OK in Eeschema but never work and
often cause a crash in Pcbnew.  This crashes all of KiCad; not just Pcbnew.
I have attached an image of the error message which I sometimes get.

Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0
Pcbnew: Zone visibility and add zone buttons use the same icon. (lp:#1818867)

[Original report](https://bugs.launchpad.net/bugs/1818867) created by **BobZ18188 (bobz18188)**
```
Pcbnew has two different buttons with the same icon.  One is "Show filled
areas in zones."  The other is "Add filled zones."  I am in the process of
learning KiCad.  I wanted to add a filled zone.  The instructions showed
the button icon.  I clicked on wrong button with the right icon.  This did
not work.  I tried it a few times to confirm but was stuck.  I probably
assumed that two buttons with the same icon would have the same function.

As a MINIMAL change, one way would be to (mirror or rotate) the icon on one
button relative to the other so that they are not identical.  That would at
least hint to the beginner following instructions that these two buttons
might be different.

Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew ui

Story points: 10.0
Zone fill can create DRC errors (lp:#1818752)

[Original report](https://bugs.launchpad.net/bugs/1818752) created by **Seth Hillbrand (sethh)**
```
When filling with certain combinations of thermal clearance and thermal
spoke width, pcbnew can generate zone fills that violate DRC.

The attached board shows a minimal example.  In this board, there is a
small track below pad 16 that causes two zone areas to appear on both
sides.  The zone areas overlap tracks and cause DRC errors.

Removing the track stub and/or modifying the zone parameters sufficiently
will cause the bad fill to correct itself.

Application: pcbnew
Version: (5.1.0-rc2-38-g4612175da2), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-2-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: Clang 7.0.1 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 8.0
Scrollbars in eeschema sometimes jump by a large amound (lp:#1818685)

[Original report](https://bugs.launchpad.net/bugs/1818685) created by **Ron Burkey (rburkey)**
```
In eeschema, if you're zoomed in to just a small portion of the sheet and
try to use the scrollbars to slightly reposition the viewport, the viewport
will sometimes instead jump by a large amount left (if using the horizontal
bar) or upward (if using the vertical scrollbar).  In other words, if an
errant jump occurs, it always jumps to a much smaller X or Y coordinate.

By a "large" amount, I mean (for example) that if I happen to be working at
the right edge of the sheet, it may jump nearly to the left edge, or indeed
even beyond the left edge so that it's outside of the sheet altogether.

I have been dealing with this particular problem for many months, but have
been unable to characterize exactly when this happens.  It happens,
perhaps, 10% of the time.  I will note, however, that I typically use a
grid size of 25 mils rather than the default 50, and sometimes use a grid
size of 5 mils for a very small bit of editing, and that the jumps
subjectively occur more frequently if zoomed in a lot at a small grid size.
At any rate, whether it's objectively more frequent then or not, it's the
time when it's most annoying, because it's the most time-consuming to try
to find the patch you were working on before it happened, so it definitely
stands out the most in my memory.

Version info:

Application: kicad
Version: 5.1.0-rc2-unknown-4612175~81~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 10.0
Field Name Templates settings do not respect default text size (lp:#1818668)

[Original report](https://bugs.launchpad.net/bugs/1818668) created by **Ron Burkey (rburkey)**
```
In the eeschema preferences, it's possible to set a default text size.
It's also possible to use the Field Name Templates settings to define
fields which will always be added to components placed on the schematic.
However, these Field Name Templates do not respect the default text size
setting.  Nor is there any other way to set the text sizes for them.
Instead, they are always sized at 50 mils.  (Nor is there any way to
specify the Italic or Bold settings these extra fields should have.)

The result is that while it's convenient to use the Field Name Templates to
make sure the desired fields always exist, if you don't want these fields
to be 50 mils with no italics or bold, it's necessary to edit EACH
component manually in order to get the text size and/or italic/bold
settings for them correct.  Needless to say, that can be quite
inconvenient.

Here is my version info:

Application: kicad
Version: 5.1.0-rc1-unknown-235f2c7~76~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Bad move / grid interaction (lp:#1818667)

[Original report](https://bugs.launchpad.net/bugs/1818667) created by **Ron Burkey (rburkey)**
```
In the schematic editor, if you are moving something (say, with 'M', or
'G', or by duplicating a block, etc.) by a small amount, it used to be very
convenient to do so with the arrow keys.  It used to be that each press of
an arrow key would move the item by exactly one grid position.

That is no longer the case, and hasn't been so for perhaps 6-8 months.
What happens now is that pressing an arrow key makes the item jump by a
very large amount.  (I can't quite characterize how much it jumps, since
it's not always the same, and seems to depend on the zoom level.  But it
may be about 10% of the viewport size.)

Now, unfortunately, if you want to move an item by a small amount, you have
to try and judge it precisely with the mouse, which is very tricky.

Version info:

Application: kicad
Version: 5.1.0-rc1-unknown-235f2c7~76~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 14.0
No option for centering bitmaps in page layout editor (lp:#1818664)

[Original report](https://bugs.launchpad.net/bugs/1818664) created by **Ron Burkey (rburkey)**
```
The ability to place a bitmap in the page-layout editor is very convenient,
but if you need to center the bitmap (which I do all the time) it is quite
inconvenient because you have to manually calculate the position.

It would be nice instead if you could position the bitmap relative to the
center (rather than to corners), or if there was a button (or some other
mechanism) that populated the StartX and StartY boxes with the page's
center coordinates.

Here's my version info.

Application: kicad
Version: 5.1.0-rc1-unknown-235f2c7~76~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pleditor

Story points: 6.0
Add thicknesses of layers and isolation layers in stack up editor (lp:#1818608)

[Original report](https://bugs.launchpad.net/bugs/1818608) created by **Urs Obernolte (urs-obernolte)**
```
It would be nice to have the copper thicknesses in the stack-up editor and
isolation-layers with thicknesses and material. That combined with an
export function would make the manufacturing-data more complete.

Also it would flatten the track for calculation tools of track impedances.
(like in qucs / qucsstudio where it could be integrated from, sourcecode is
available)

But having all that in mind it shows that these information about stack up
is needed to share over the whole project and needs to be defined/saved in
the project file or should be even visible in the schematics entry.
```
Original tags: feature.request

Story points: 8.0
eeschema - create new component in libeditor - max units 26 in comps (lp:#1818471)

[Original report](https://bugs.launchpad.net/bugs/1818471) created by **Andrey Fedorushkov (faa)**
```
eeschema - create new component in libeditor - max units 26 in component

in files
dialog_lib_new_component_base.[cpp|fbp]
set limit to 26 units

screenshot attached.

KiCad build from last master.
```

Story points: 6.0
Cannot select footprint text on copper layer (lp:#1818449)

[Original report](https://bugs.launchpad.net/bugs/1818449) created by **Andrzej Wolski (awolski)**
```
When the active layer is one on the front layers (F.Cu, F.SilkS, etc.) I
cannot select footprint text placed on F.Cu layer.
Similar behavior can be observed for text on B.Cu when active is one of the
bottom layers.
Selecting fp text on other layers seems to be fine.

Attached board for testing.

Application: pcbnew
Version: (5.1.0-rc2-26-g643d884fd), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.57.0 OpenSSL/1.0.2n (WinSSL) zlib/1.2.11 libidn2/2.0.4
libssh2/1.8.0 nghttp2/1.29.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.66.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.57.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew

Story points: 6.0
Edit symbol fields: <enter> in grid exits the dialog [MSW only] (lp:#1818426)

[Original report](https://bugs.launchpad.net/bugs/1818426) created by **Mathieu Stephan (limpkin)**
```
version 5.1.0-rc2-21-g16b3c80a7

when opening the edit symbol fields window and double clicking on a field
to edit, the enter key makes the whole window save & close. Expected
behavior is saving the field and leaving "edit mode"
```
Original tags: eeschema ui windows

Story points: 6.0