From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 10399@debbugs.gnu.org
Subject: bug#10399: [PATCH] Document win32 font backends
Date: Sat, 31 Dec 2011 03:41:46 -0800 [thread overview]
Message-ID: <4EFEF4FA.4080701@dancol.org> (raw)
In-Reply-To: <83ty4hrnn8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On 12/31/11 3:22 AM, Eli Zaretskii wrote:
> If a MinGW build of Emacs can use DirectWrite, and if there will be no
> copyright issues with providing the missing headers and interface
> libraries, then feel free to work on adding DirectWrite support to
> Emacs. Thanks in advance.
What exactly is the legal situation surrounding headers? Would copying
and modifying declarations from the Microsoft headers or MSDN be
acceptable, considering that there is really only one way to describe
what a function is called and what parameters it takes? If not, how
exactly would one create untainted declarations?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2011-12-31 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:06 bug#10399: [PATCH] Document win32 font backends Daniel Colascione
2011-12-29 16:21 ` Juanma Barranquero
2011-12-29 16:57 ` Eli Zaretskii
2011-12-29 17:16 ` Daniel Colascione
2011-12-31 10:56 ` Eli Zaretskii
2011-12-31 11:04 ` Daniel Colascione
2011-12-31 11:22 ` Eli Zaretskii
2011-12-31 11:41 ` Daniel Colascione [this message]
2011-12-31 11:48 ` Eli Zaretskii
2011-12-31 15:23 ` Óscar Fuentes
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=4EFEF4FA.4080701@dancol.org \
--to=dancol@dancol.org \
--cc=10399@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
/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).