public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Mike M. Volokhov" <mishka@apk.od.ua>
To: Chad Walstrom <chewie@wookimus.net>
Cc: help-gnats@gnu.org
Subject: Re: Gnats{web} localization
Date: Thu, 30 Sep 2004 16:57:00 -0000	[thread overview]
Message-ID: <20040930113252.5bb58ffb.mishka@apk.od.ua> (raw)
In-Reply-To: <20040929180923.GJ8820@wookimus.net>

On Wed, 29 Sep 2004 13:09:23 -0500
Chad Walstrom <chewie@wookimus.net> wrote:

> Mike, I'm all for l12n and i18n of GNATS and gnatsweb.  Mel H. is
> planning on adding a data abstraction layer API to gnats so that
> different backends may be used.  In fact, he has already written the
> code to support Oracle and is working on PostgreSQL, currently.  XML
> could certainly be one of those implementations.

Very nice idea! I seen something on TODOs, but you have explained this
for me, thanks. Is this work available anywhere for tests?

> 
> Mike M. Volokhov wrote:
[snip]
> > 1) Add yet another field to Gnats PR structure: ">Encoding:". The Gnats
> >    will use UTF-8, for example, as internal charset encoding.
> 
> Great idea.
> 
> > 2) Use XML as internal format for database processing. This allows use
> > power and simplicity of XML i18n.
> 
> See above.
> 
> I'd love to see this fleshed out.  Does anyone have any driving opinions
> as to which we should pursue.  I don't know how large of an impact #1
> would have on the code base, as I'm not that familiar with it yet.

The GNATS have clear enough API and I think this feature can be added
within minimal work. However, it will depends on two libraries more:
iconv and MIME. But again, IMHO it cost this.

If you approve this work I'll start coding and will publish patches ASAP
just after finishing.

> #2 probably won't happen until we get Mel's new API in place.

Yep, it is. Moreover, charset or language specification is needed in any
case. If new API could handle arbitrary "frontend" (i.e. input PR
format) too, then it would be possible to submit XML reports within any
charset (or even any charset for parts of PR).

Will be waiting for Mel H.

> 
> On a personal note, the delivery date of our first child is quickly
> approaching.  Either my wife will be induced tonight or Friday,
> depending upon how the lab tests turn out later today.  I will likely be
> off the radar for the next couple weeks.

Well, I'm pretty sure anything will be good!

--
Mishka.


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

      reply	other threads:[~2004-09-30  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 18:10 Mike M. Volokhov
2004-09-30  8:34 ` Chad Walstrom
2004-09-30 16:57   ` Mike M. Volokhov [this message]

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

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

  git send-email \
    --in-reply-to=20040930113252.5bb58ffb.mishka@apk.od.ua \
    --to=mishka@apk.od.ua \
    --cc=chewie@wookimus.net \
    --cc=help-gnats@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.
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).