unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25864@debbugs.gnu.org, mandar.mitra@gmail.com
Subject: bug#25864: 25.1; Incorrect rendering for Bengali compound character
Date: Wed, 1 Mar 2017 10:10:22 -0800 (PST)	[thread overview]
Message-ID: <2e6078ab-131b-4b00-ba9d-912cc49f0b41@default> (raw)
In-Reply-To: <<8360jsophb.fsf@gnu.org>>

> > > Yes, but it makes little sense to me to add information there which is
> > > about something two orders of magnitude trickier than anything else on
> > > the wiki.
> >
> > So your problem is not, as you said, inability to "find any good place
> > [for it] there."  You don't think such content belongs on the wiki.
> 
> I thought it did, but as I see no stuff there of a similar nature, or
> anything close, it seems like the wiki is not for such issues.  Thus
> "no good place".

The wiki is about anything about Emacs.  It's of course up to
you whether you want to include such info there.

But just because you do not find other, similar info there is
no reason to suppose that such info does not belong on the wiki.

Users of the wiki add whatever topics they think might help
others who use or are interested in Emacs.





       reply	other threads:[~2017-03-01 18:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<<87bmtl5fwx.fsf@gnu.org>
     [not found] ` <<<<83d1e1nexa.fsf@gnu.org>
     [not found]   ` <<<80b987d9-9200-44af-86cf-c6b81ef13435@default>
     [not found]     ` <<<837f48orco.fsf@gnu.org>
     [not found]       ` <<07fd0e8a-0214-4ed3-9cc8-97cb471fdd69@default>
     [not found]         ` <<8360jsophb.fsf@gnu.org>
2017-03-01 18:10           ` Drew Adams [this message]
     [not found] <<<87bmtl5fwx.fsf@gnu.org>
     [not found] ` <<<83d1e1nexa.fsf@gnu.org>
     [not found]   ` <<80b987d9-9200-44af-86cf-c6b81ef13435@default>
     [not found]     ` <<837f48orco.fsf@gnu.org>
2017-03-01 17:14       ` bug#25864: 25.1; Incorrect rendering for Bengali compound character Drew Adams
2017-03-01 17:50         ` Eli Zaretskii
     [not found] <<87bmtl5fwx.fsf@gnu.org>
     [not found] ` <<83d1e1nexa.fsf@gnu.org>
2017-03-01 16:57   ` Drew Adams
2017-03-01 17:10     ` Eli Zaretskii
2017-02-23 22:15 Mandar Mitra
2017-02-24 18:14 ` Eli Zaretskii
2017-02-25 15:05   ` Mandar Mitra
2017-02-25 15:29     ` Eli Zaretskii
2017-02-27 14:01       ` handa
2017-02-27 15:05         ` Mandar Mitra
2017-02-28 16:25           ` handa
2017-02-28 19:21             ` Mandar Mitra
2017-02-28 19:48               ` Eli Zaretskii
2017-03-01 12:40               ` handa
2017-03-01 16:24                 ` Eli Zaretskii
2017-03-04 14:02                   ` handa
2017-03-04 14:31                     ` 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=2e6078ab-131b-4b00-ba9d-912cc49f0b41@default \
    --to=drew.adams@oracle.com \
    --cc=25864@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mandar.mitra@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).