Closed Bug 135604 (bz-german) Opened 23 years ago Closed 20 years ago

german translation of Bugzilla templates

Categories

(Bugzilla :: User Interface, enhancement, P3)

2.15
enhancement

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: nn4l, Assigned: nn4l)

References

()

Details

Attachments

(2 obsolete files)

This bug is a placeholder for the translation of Bugzilla templates into german
language. 
Announce the file(s) you are going to translate, and upload them as an
attachment when it is done.
I'm currently working on template/default/query/query.atml .
Suggestion: wait a week or so after a given template is checked in before
localising it. Often bugs are shaken out in the short time after release, and
you'd end up spending unnecessary time copying those changes into your localised
files.

Suggestion 2: Each localised template, as well as having a template version
string, states which CVS version of the original template it is based on. This
gives people something to work from if they are trying to update it.

Gerv
Tobias, you wrote in bug 126955: 
> I have a "default/de/" ready sitting here, if someone wants to check it in, 
> drop a mail.

Is this still valid? Can you comment here about the current status?
Depends on: bz-l10n
Can someone post a list of already templated files which are already under
translation by anyone: I want to have a hint where to start my translation
effotrs...
I woukld start with the stuff in show/* . Can someone post an already translated
template so thet I can get some idea how it works? And, are there any
bugzilla-specific coding guidelines BEFORE we start?
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
I will upload query.atml after merging with the latest cvs version.
The translation was very 
easy.

There are still many english words in the cgi code, so even after translating all text 
in a template the output is a mishmash of german/english, such as sort order, status, resolution 
etc.
This bug shouldn't be targetted at 2.16. :-)

The Bugzilla team has a plan to make Bugzilla localisable. A small amount of
work needs to be done for 2.16 to facilitiate this; after that, localised
template packs can be used. But the de translation will not be checked in for
2.16 (if ever; that's an open question for all translations), so I'm
retargetting this bug.

Hope that's OK.

Gerv
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Attached file query.atml, based on cvs version dated 2002-04-11 (obsolete) (deleted) —
I'm now working on buglist/*
Hallo, (back to read emails after a long time)
Questions:
- How to handle " for German: »...« or "..."?
- How to translate Quality Assurance (QA) in attachment 78875 [details]
  this is "QS" (Qualitätssicherung?)

Regarding
pref/* all except on file doesn't contain "1.0@bugzilla.org", should I fill a
bug report?
This is by the way the area where I want to attach files next (after I updated
my rotting raw translation)

> But the de translation will not be checked in for 2.16 (if ever; that's an 
> open question for all translations)
I'd like to see the translations in CVS. I think it would be easier if Bugzilla
would have its own CVS tree then the translations could e.g. put into a
different module. Keeping the translations and bugzilla in the same module (or
better the translations in a subdirectory of bugzilla) will enforce more
pressure to make sure that all translations are up to date.
Maybe mozilla/webtools/bugzilla-trans as directory would be a solution.
One can then do a "cd bugzilla/templates/default; cvs co .../bugzilla-trans/de
-d de".
Regarding attachmen 78875:
> email Adresse
How should we spell "email"? The Duden suggests "E-Mail" thus "E-Mailadresse"?
Attached file de/index.tmpl - 1.4/Fri Apr 12 15:19:45 2002 (obsolete) (deleted) —
I used "Fehlerbericht" rather than "Bug". We should try to get a consistent
name for "bug"
Tobias:

I never looked into bugzilla templates yet but I know Mozilla German project... ;-)

so my thoughts:

> - How to handle " for German: »...« or "..."?

As Bugzilla should work good on possibly all browsers (not only the newer ones),
and &rdquo;/&rdquo;/&bdquo; are HTML 4.0 (&raquo;/&laquo; are "<<" and ">>" and
quite uncommon, I think), I wouldn't use them.
Note that "..." get more and more commen here as well, and Mozilla German uses
"...", too.

- How to translate Quality Assurance (QA) in attachment 78875 [details]
  this is "QS" (Qualitätssicherung?)

In Mozilla German, I'm using a German translation but the original (English)
abbrevation if the German abbrevation isn't common.
I believe that People working with other (non-German) Bugzilla implementations
will always prefer "QA-Kontakt" to "QS-Kontakt", and I also believe it's bad to
invent many new words or Abbrevations that also advanced users have to learn newly.
Tobias:
BTrw, Mozilla Gemran is using "E-Mail" / "E-Mail-Adresse" and, though it's not
nneded much, "Bug" - I never heard people speking about "Fehlerberichte" but
quite often of "Bugs" in German, I even heard "DAUs" speaking of "Microsoft-Bugs"...
I will make a lookup table (english word/phrase --> german word/phrase), so 
that we are consistent throughout the text, and maybe a script for globally 
changing them.

We really need CVS access for this type of project. If checkin privileges are 
restricted within the Mozilla project (understandable), then I would like to 
set up a CVS account on Sourceforge or somewhere else.
I put some translations at:
http://www.physik.fu-berlin.de/~tburnus/bugzilla/bugzilla-de.tar.gz
 I'm not convinced that I've always chosen the most suitable translation,
 especially "vote" and even more "voter" are hard to translate
docs/README.templates-de -- contains the translation table I used
docs/changelog.template-de
template/default/de/index.tmpl
template/default/de/pref/email.tmpl
template/default/de/pref/account.tmpl
template/default/de/pref/footer.tmpl
template/default/de/pref/permissions.tmpl
template/default/de/pref/userprefs.tmpl
template/default/de/global/choose_product.tmpl
template/default/de/global/code-error.html.tmpl
template/default/de/global/user-error.html.tmpl
template/default/de/global/message.html.tmpl
template/default/de/sidebar/xul.tmpl
template/default/de/admin/account_created.tmpl
template/default/de/admin/account_exists.tmpl
template/default/de/admin/create_account.tmpl
template/default/de/admin/change-password.html.tmpl
template/default/de/info/quips.tmpl
template/default/de/info/describe-keywords.html.tmpl
template/default/de/info/describe-components.tmpl
An updated version is at
http://www.physik.fu-berlin.de/~tburnus/bugzilla/bugzilla-de.tar.gz
(adapted to new directory structure, more templates translated, still neither
complete nor contains the best translations in every case)
I updated it again and changed the URL a bit. See:
http://www.physik.fu-berlin.de/~tburnus/bugzilla/
I started with a SF project for the German Bugzilla.
Everything is still a bit rough (the translations as well as the pages) but I
imported my Bugzilla 2.17 tree in to CVS. (Bugzilla 2.16: still do to)

The web pages need also some polishing.
  http://bugzilla-de.sf.net/
Alias: bz-german
Attachment #78875 - Attachment is obsolete: true
Attachment #78914 - Attachment is obsolete: true
Depends on: 182975
I'm currently working on a german translation of the Bugzilla Administration
Guide (Chapter 5).
Arne,
If you like, you can rely on parts of my german documentation of Bugzilla, which
was based on 2.16. Download at
http://www.netzwissen.de/archiv/pdf/bugzilla_de.pdf (170 k) - other file formats
on request ;-)
First parts of the german Bugzilla handbook are here:

http://www.softwaretesting.de/article/archive/9/

I'm now digging through the DocBook documentation, so that future releases will
be in docbook format too.
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Is this bug still useful?
Apparently not.
[http://www.bugzilla.org/download/#localizations]
Status: NEW → RESOLVED
Closed: 20 years ago
No longer depends on: 182975
Resolution: --- → WORKSFORME
clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.
Target Milestone: Bugzilla 2.22 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: