[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unicode support for the MS Windows clipboard [new patch]

From: Eli Zaretskii
Subject: Re: Unicode support for the MS Windows clipboard [new patch]
Date: Mon, 13 Sep 2004 22:55:19 +0300

> Cc: address@hidden,  address@hidden,  address@hidden
> From: Benjamin Riefenstahl <address@hidden>
> Date: Sun, 12 Sep 2004 21:50:14 +0200
> "Eli Zaretskii" <address@hidden> writes:
> > I don't think the documentation of this should go into msdog.texi.
> > That section is for the MS-DOS port, and in the printed version it
> > goes into an appendix.  Windows users will not expect to find it
> > there.
> Well, as my defense, I seem to remember that folks on this list were
> asked to look at the MS-DOS sections of the manual for
> Windows-specific questions.  Also the index item "Windows clipboard
> support" actually points to msdog.texi.  Maybe this should better be
> "Windows clipboard support on MS-DOS", than.

People were referred to the DOS section because in the past there was
no better place to look; historically, it so happened that the DOS
port was documented much better than the Windows port.  I believe this
is no longer the case.

The issues specific to the Windows port should IMHO be either in the
body of the manual or in a Windows-specific appendix.  This calls for
a volunteer; but once this is done, I promise to go through msdog.texi
and fix it so that it unequivocally refers to the MS-DOS port.

> > I think we should leave msdog.texi alone and instead put the
> > Windows-related text into mule.texi (since the only different aspect
> > is the encoding/decoding issue).
> While set-selection-coding-system is discussed there shortly, neither
> the default value nor any reason to customize it is actually
> mentioned.  There may not be much reason to discuss actual
> customization options for X11 but there is even less reason on
> Windows.  So maybe we don't need any additional documentation here at
> all?

I think the clipboard handling is special enough to warrant some text
about it.  But that is just my HO; if the Windows experts think this
doesn't need to be documented, I won't object.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]