Patch to resolve archlinux build warn/errors.

Signed-off-by: Bert Timmerman <bert.timmerman@xs4all.nl>
src/Makefile.am: revert the AM_CPPFLAGS change as it breaks the building process.

Signed-off-by: Bert Timmerman <bert.timmerman@xs4all.nl>
Additional checks for existing names

In ActionElementList, add an additional check for DESCRIPTION_NAME(e)
before comparing with an old footprint.
src/res_parse.y: handle resource globals gracefully.

Likely, res_file is used somewhere to check something. In case a
resource file was loaded earlier, but the current parsing is from
a string, res_file is still != NULL, so this check would mislead.

Solution: Clear res_file and res_filename as soon as the file
          behind it gets closed.

Also replace a number of zeros with the more appropriate NULL.

Affects-bug: lp-1206882
src/action.c: add a number of comments.

... in the hope they're right.
Add intl/plural.c to POTFILES.skip
Make xy file output IPC 7531 compliant.

Improved code style by Bert Timmerman <bert.timmerman@xs4all.nl>.
Regenerate tests after "Make xy file output IPC 7531 compliant.".
Fix lockup when a scroll event is received outside the drawing area

This can occur if the user is dragging a component in the drawing area (hence
a pointer grab is in operation), and during this drag, the user moves the mouse
outside the drawing area and touches the scroll wheel.

We then hit the scroll event handler, mouse action handler, action dispatcher
etc.. and find we do not have a current location known. (The cursor is outside
the drawing area).  We then prompt for a location, and using a recursive main-
loop, wait for some kind (e.g. a mouse click) which gives one.

The problem appears to be caused by the fact it is likely we get a second
scroll event with the first, and that we process this from within the recursive
main-loop. We are still outside the drawing area, so prompt the user for a
location, and enter another level of recursion. (In my tests, I was able to hit
6 or 7 levels deep of main-loop recursion).

Our code fails to exit its recursive main-loop if it rucurses, and in any case,
we would not want to prompt the user "n" times in a row. The failure to exit
from recursion is probably due to the event handlers attached by the first
recursive main-loop being called prior to those attached later. (We attempt to
quit the first recursive main-loop, but cannot, as there are others now running).

As a quick work-around to the immediate problem, prevent scroll events being
received from within the recursive main-loop. This prevents the lockup, but
ideally we should re-think how we handle these events to avoid requiring the
user to click on a coordinate.

I have also added a GDK_THREADS_{LEAVE,ENTER} pair around running the main-loop,
as this is what GTK's code does for gtk_dialog_run().
fix missing ) typo in changeclearsize_syntax

Signed-off-by: bert <bert.timmerman@xs4all.nl>
add missing option splitlines in djopt_syntax

Signed-off-by: bert <bert.timmerman@xs4all.nl>
Added pt_BR translation file.

Signed-off-by: bert <bert.timmerman@xs4all.nl>
Fix .res.in to .res.h in POTFILES.in

Affects-bug: lp-913458
Fix menu gettextization

Changes were made to eliminate errors output by 'make distcheck'
or 'make -C po update-po'.

Closes-bug: lp-913458
Menu items i18n

This adds i18n for gtk menus

Closes-bug: lp-1113758
gerber.c: added an option for Hackvana file name convention.

Signed-off-by: bert <bert.timmerman@xs4all.nl>
Use ngettext for message with plural form

Signed-off-by: bert <bert.timmerman@xs4all.nl>
pt_BR language update

Signed-off-by: bert <bert.timmerman@xs4all.nl>
Updated Russian translation

Signed-off-by: bert <bert.timmerman@xs4all.nl>
Use gettext.h for pgettext()

Signed-off-by: bert <bert.timmerman@xs4all.nl>