unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Da_vid via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72198@debbugs.gnu.org
Subject: bug#72198: 31.0.50; `svg-print' add useless and possibly wrong space in XML representation.
Date: Sat, 03 Aug 2024 17:08:25 +0200	[thread overview]
Message-ID: <94933CBA-598B-437D-852D-C1AA00F264BC@orange.fr> (raw)
In-Reply-To: <11741141-DA4A-4281-9B81-7C8C94BEAD36@orange.fr>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

Le 27 juillet 2024 16:45:12 GMT+02:00, Da_vid <da_vid@orange.fr> a écrit :
>Le 27 juillet 2024 09:19:36 GMT+02:00, Eli Zaretskii <eliz@gnu.org> a écrit :
>>> Date: Fri, 19 Jul 2024 16:10:00 +0200
>>> From:  David Ponce via "Bug reports for GNU Emacs,
>>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>> 
>>> Since the extra space in front of the XML representation of each child
>>> node is unnecessary according to the SVG 1.1 specification, the attached
>>> V0 patch resolves this issue by removing the offending statement.
>>> 
>>> The attached V1 patch is a proposal to go a step further by improving
>>> the documentation and using the DOM API to access parts of dom node.
>>
>>Thanks.  Can you elaborate on what should we consider in order to
>>decide whether to install V0 or V1?
>
>The V0 patch is the only one required to fix the reported bug.
>
>V1 is just a proposal to improve the doc string and avoid to access dom data using knowledge of the internal representation instead of the dom api.
>V1 also include the fix in V0.
>
>I hope it's clearer now.
>Thanks
Hello Eli,
Do you need more details from me to progress in resolving this bug?
Thanks

[-- Attachment #2: Type: text/html, Size: 1921 bytes --]

  reply	other threads:[~2024-08-03 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 14:10 bug#72198: 31.0.50; `svg-print' add useless and possibly wrong space in XML representation David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27  7:19 ` Eli Zaretskii
2024-07-27 14:45   ` Da_vid via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-03 15:08     ` Da_vid via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-03 15:46       ` Eli Zaretskii
2024-08-03 22:38         ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04  7:20     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94933CBA-598B-437D-852D-C1AA00F264BC@orange.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=72198@debbugs.gnu.org \
    --cc=da_vid@orange.fr \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).