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


[-- Attachment #1.1: Type: text/plain, Size: 2006 bytes --]

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.

Mike M. Volokhov wrote:
> So as my time was limited, I've just changed header{} at mail-format{}
> section as follows:
> 
> 	header {
> 	  format "Content-Type: text/plain; charset=koi8-r\nSubject: Re: %s/%s\n"
> 	  fields { "Category" "Number" } 
> 	}

I used this method to add "Priority: junk" to all GNATS autoresponses.
Great idea.

> I.e. Subject now doesn't contains synopsis text, and message have a
> Content-Type field. 

GNATS flexibility shining through once again, I'd say.

> Second, I need complete localization for Gnats. I.e. all messages,
> field names, categories and so on should be easy changed by site's own
> values on any preferred language. I'm personally have two ideas for
> this:
> 
> 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.  #2
probably won't happen until we get Mel's new API in place.

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.

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

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

  reply	other threads:[~2004-09-29 18:10 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 [this message]
2004-09-30 16:57   ` Mike M. Volokhov

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=20040929180923.GJ8820@wookimus.net \
    --to=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).