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 683387 - Typos in strings
Typos in strings
Status: RESOLVED FIXED
Product: vino
Classification: Applications
Component: Preferences Dialog
3.5.x
Other All
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-05 08:01 UTC by Chris Leonard
Modified: 2012-10-20 07:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Chris Leonard 2012-09-05 08:01:41 UTC
1) typo "eg > e.g." or use "for example"

  ../common/org.gnome.Vino.gschema.xml.h:8


"If not set, the server will listen on all network interfaces.

Set this if you want that accept connections only from some specific network interface. eg: eth0, wifi0, lo, ..."

should be:

"If not set, the server will listen on all network interfaces.

Set this if you want that accept connections only from some specific network interface. e.g.: eth0, wifi0, lo, ..."

2) typo "Universal Plug and Play" is abbreviated UPnP not UPNP

  ../common/org.gnome.Vino.gschema.xml.h:32

"Whether we should use UPNP to forward the port in routers"

should be:

"Whether we should use UPnP to forward the port in routers"


3) typo "Universal Plug and Play" is abbreviated UPnP not UPNP

  ../common/org.gnome.Vino.gschema.xml.h:33

"If true, we will use UPNP protocol to automatically forward the port used by vino in the router."

should be:

"If true, we will use UPnP protocol to automatically forward the port used by vino in the router."
Comment 1 David King 2012-09-05 12:55:42 UTC
(In reply to comment #0)
> 1) typo "eg > e.g." or use "for example"

I think that ‘for example’ would be the best choice.

> 2) typo "Universal Plug and Play" is abbreviated UPnP not UPNP
> 3) typo "Universal Plug and Play" is abbreviated UPnP not UPNP

Agreed, although those strings could do with being rewritten regardless.

All of these changes will happen in the next development release, after the string freeze (and therefore will not be fixed in 3.6).
Comment 2 Chris Leonard 2012-09-05 17:04:05 UTC
Fair enough on holding for next release, these have minor impact. I just file these as I see them and I'm sorry for the apparent "pickiness", but coming from Sugar Labs downstream (where the strings land on millions of children's desktops), I think i18n improvements like this are valuable, no matter how small.
Comment 3 David King 2012-10-20 07:54:45 UTC
Fixed in master in commit f37ca213fda500ea2f93d005e945644c2f2e5721, thanks.