From: "Micone, Andrew (Manpower Contract)" <andrew.micone@hp.com>
To: "Leu, Fa. PostDirekt MA" <H-J.Leu@deutschepost.de>, <help-gnats@gnu.org>
Subject: RE: GNATS help needed
Date: Thu, 16 Oct 2003 17:17:00 -0000 [thread overview]
Message-ID: <E7BC9AA1C77D634D8255A878AB49B09D05005714@cceexc19.americas.cpqcorp.net> (raw)
I can't say what you could do to recover, but I can give you some localization advice. As far as I understand it, and I've had good success with customizing GNATS, it only supports basic ASCII in its data files and doesn't have any localization support. That doesn't mean you couldn't localize it, I've localized worse (i.e. printer firmware). If you were going to localize it, a generic localization approach would be:
A) Use the field names as keys to a string resource database and map them to localized string displays in the user-interface. So don't change "Closed-Date" to something else, leave it as-is and then map it to its german string through a lookup table and some additional user-interface code.
B) You would need to check over the I/O and indexing routines to make sure they can support the character set you are using. You could do this in increasingly levels of complexity by either kludging your character set into ASCII with escape codes, programming support for eight-bit character sets (I think most european languages can be handled in eight bits), or go all out and change it so that it supports unicode strings opaquely. GNATS expects mail-like messages. If you look at how file attachments are handled, they are converted into something that looks like uuencoded ASCII. You would need to do something similair with foreign character sets, especially if you wanted to do it right by using Unicode.
Anyway, not having explored the code in too much depth, that's my $0.02 USD.
Andy Micone
Performance Engineer / Process Lead
Performance R&D
(208) 396-4228 andrew.micone@hp.com
-----Original Message-----
From: Leu, Fa. PostDirekt MA [mailto:H-J.Leu@deutschepost.de]
Sent: Thursday, October 16, 2003 8:04 AM
To: 'help-gnats@gnu.org'
Subject: GNATS help needed
Hi,
i am trying to customize and translate GNATS to have a German User Interface.
After serveral good iterations i'am stuck - since i've changed the field "Closed-Date"
send-pr won't do anything anymore and gnatsweb returns "unparseable reply from gnatsd:" (without a reply) in the directory gnats-adm a file "gnats.lock" is created. I've undone my changes but get still the same result.
1. What can i do to recover.
2. Is a translation generally possible (may be there are hardcoded fieldnames, etc)
many thanks in advance
Hans-Jörg Leu
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org http://mail.gnu.org/mailman/listinfo/help-gnats
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2003-10-16 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 17:17 Micone, Andrew (Manpower Contract) [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 15:19 Leu, Fa. PostDirekt MA
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=E7BC9AA1C77D634D8255A878AB49B09D05005714@cceexc19.americas.cpqcorp.net \
--to=andrew.micone@hp.com \
--cc=H-J.Leu@deutschepost.de \
--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).