After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 120150 - at-spi bonobo service i18n commented out
at-spi bonobo service i18n commented out
Status: RESOLVED NOTABUG
Product: at-spi
Classification: Platform
Component: general
1.3.x
Other All
: Normal normal
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks:
 
 
Reported: 2003-08-18 14:49 UTC by Dafydd Harries
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Dafydd Harries 2003-08-18 14:49:59 UTC
at-spi is not properly internationalized due to critical lines being
commented out in its configure.in:

dnl internationalization support
dnl ALL_LINGUAS="az be ca cs cy da de el eo es et fi fr he hi it ko mn ms
nl pl pt_BR pt ru sk sq sr@Latn sr sv vi zh_CN"
dnl AM_GLIB_GNU_GETTEXT

It is important that this package, part of GNOME's core, it properly
i18nised for the GNOME2.4 release.
Comment 2 bill.haneman 2003-08-18 15:04:54 UTC
well, there are only two translatable strings in all of at-spi AFAIK,
both in the Accessibility_Registry.server.in.in file.  Fairly obscure
strings, even at that.

Severity is not major IMO - but if someone wants to make sure the po
directories are building OK then I see no harm in reinstating the dnl
lines.  I don't know why they were removed, presumably a build breakage.
Comment 3 Christian Rose 2003-08-18 15:14:25 UTC
The commit comment seems to have been:

---
1.21 <baddog> 2001-12-07 13:44
Comment out extraneous i18n support temporarily
---

Perhaps the reverting of this just accidentally forgotten.

There are 4 messages in at-spi (see
http://developer.gnome.org/projects/gtp/status/gnome-2.4/PO/at-spi.HEAD.pot),
and none of them seem extremely important, but this should still
probably be fixed before the release.
Comment 4 Abel Cheung 2003-08-18 16:03:17 UTC
It was me who did it; at that time there was a build breakage, and no
translation was present at all, so I commented it out.

For now, it would probably be good to reenable it again -- or not. I
saw no *textdomain calls in source, is it useful at all to reenable
the i18n support in configure.in? If i18n of at-spi is desired, then
probably more have to be done.
Comment 5 Christian Rose 2003-08-19 09:54:45 UTC
If you have time to fix this for GNOME 2.4 so that the translations
work, then IMHO please do.
Comment 6 bill.haneman 2003-10-09 16:46:31 UTC
adding accessibility keyword
Comment 7 bill.haneman 2003-12-08 15:01:43 UTC
at-spi doesn't emit end-user strings (as a rule).  But the .server.in
i18n probably ought to be done.
Comment 8 Danilo Segan 2004-03-09 03:53:00 UTC
Bill,
If that's the case here, I'd suggest the following action:
- move bridge.c to POTFILES.skip instead of POTFILES.in (so
"intltool-update -m" won't report 'missing' files), or unmark any
strings marked there (for the same reason) -- no need to translate
strings which don't get used
- mark this as resolved

If these two strings in bridge.c (g_warning and a g_print) are
actually translated somehow, you may mark this as NOTABUG, and add
comment to configure.in that translators need not update ALL_LINGUAS.

intltool merges translations into .server files without paying
attention to ALL_LINGUAS (it uses all *.po files in po subdirectory),
so they're already merged correctly.
Comment 9 bill.haneman 2004-03-24 13:21:55 UTC
Danilo I took your advice and added POTFILES.skip.
I also added a comment to the dnl line, and am closing this bug as NOTABUG.

Thanks!