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 129492 - Inconsistent writing of "URL" and "URI" in gnome-vfs
Inconsistent writing of "URL" and "URI" in gnome-vfs
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: Other
cvs (head)
Other All
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-16 21:47 UTC by Christian Rose
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Rose 2003-12-16 21:47:41 UTC
#: schemas/desktop_gnome_url_handlers.schemas.in.h:11
msgid "Set to true to have a program specified in command handle callto URLs"

#: schemas/desktop_gnome_url_handlers.schemas.in.h:21
msgid "URL handler for callto uris"

etc.

How come URL is written in uppercase, while URI is not? IMHO both should be
in uppercase. Words made out of acronyms (like "uris") is difficult to
translate.
Comment 1 Christophe Fergeau 2003-12-16 22:24:51 UTC
If you have time to commit a fix for that (uppercase URI and URL),
that would be great. These acronyms should only occur in gconf key
descriptions, which doesn't make it too critical for translations.
Comment 2 Christian Rose 2003-12-16 22:35:42 UTC
Unfortunately, there is no system that allows for prioritizing
different translatable messages inside the same module/pot file to
translators. A translatable message is a translatable message and is
shown and counted as such, regardless where it comes from.

Hence it's important to try to maintain the same linguistic quality in
all messages, regardless if it's in the UI or in schemas messages, to
not make the work of translators unnecessarily difficult.
Comment 3 Christian Neumair 2003-12-19 22:52:55 UTC
Patch committed. Closing.

regs,
 Chris
Comment 4 Christian Rose 2003-12-21 22:25:37 UTC
This was really a duplicate of bug 120740.

*** This bug has been marked as a duplicate of 120740 ***
Comment 5 Christian Rose 2003-12-21 22:28:24 UTC
D'oh, wrong bug! Sorry.