Re: translate

[Jason Alderman]

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; }


Sent from Yahoo Mail for iPhone


On Friday, May 27, 2016, 7:00 AM, dev-l10n...@lists.mozilla.org <dev-l10n...@lists.mozilla.org> wrote:

Send dev-l10n mailing list submissions to
    dev-...@lists.mozilla.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.mozilla.org/listinfo/dev-l10n
or, via email, send a message with subject or body 'help' to
    dev-l10n...@lists.mozilla.org

You can reach the person managing the list at
    dev-l10...@lists.mozilla.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dev-l10n digest..."


Today's Topics:

  1. Re: Don't translate example.* domains in error messages
      (Rimas Kudelis)
  2. Re: Don't translate example.* domains in error messages
      (Sebastian Hengst)
  3. Re: Don't translate example.* domains in error messages
      (Kim Ludvigsen)
  4. Re: Don't translate example.* domains in error messages
      (Francesco Lodolo [:flod])
  5. Re: Localization feedback for date/time picker (Philipp Kewisch)


----------------------------------------------------------------------

Message: 1
Date: Thu, 26 May 2016 22:24:16 +0300
From: Rimas Kudelis <r...@akl.lt>
To: dev-...@lists.mozilla.org
Subject: Re: Don't translate example.* domains in error messages
Message-ID: <T5idnTw2xPH70NrK...@mozilla.org>
Content-Type: text/plain; charset=utf-8

Fixed for Lithuanian.
Although I consider this just as much a drawback as an improvement.
Examples in a language one doesn't necessarily understand don't make
that much sense, and I seriously doubt that just mentioning some domain
name as an example might get us or anyone in any sort of legal trouble.

Anyway, here's what I found along the way: Calendar contains a string
where the example domain is myserver.com:

https://transvision.mozfr.org/?repo=aurora&search_type=entities&recherche=calendar/chrome/calendar/calendar.dtd:calendar.publish.example.url.description

Regards,
Rimas


------------------------------

Message: 2
Date: Thu, 26 May 2016 22:05:56 +0200
From: Sebastian Hengst <ar...@gmx.de>
To: dev-...@lists.mozilla.org
Subject: Re: Don't translate example.* domains in error messages
Message-ID: <0df59435-6661-21df...@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed

-------- Original-Nachricht --------
Betreff: Re: Don't translate example.* domains in error messages
Von: Francesco Lodolo [:flod] <fl...@lodolo.net>
An: dev-...@lists.mozilla.org
Datum: 2016-05-25 16:18
> As explained, the only valid alternatives to example.com are similar
> domains owned by national registration authorities and created for the
> same purpose.
>
> Unregistered domains, registered domains without active web pages,
> parking pages are definitely not OK.

You can also use .example as top level domain to create partially
localized domains, see the second page of
https://tools.ietf.org/html/rfc2606 , e.g.

<localized "example">.example

For German, we used that for the email placeholder in the Firefox OS
email app.

Sebastian


------------------------------

Message: 3
Date: Thu, 26 May 2016 22:43:44 +0200
From: Kim Ludvigsen <lud...@kimludvigsen.dk>
To: dev-...@lists.mozilla.org
Subject: Re: Don't translate example.* domains in error messages
Message-ID: <ytOdnWOkVcKV_drK...@mozilla.org>
Content-Type: text/plain; charset=utf-8; format=flowed

Den 26-05-2016 kl. 21:24 skrev Rimas Kudelis:
> Fixed for Lithuanian.
> Although I consider this just as much a drawback as an improvement.
> Examples in a language one doesn't necessarily understand don't make
> that much sense, and I seriously doubt that just mentioning some domain
> name as an example might get us or anyone in any sort of legal trouble.

You will never get in *legal* trouble for linking to a page in this context.

But consider this: You use the available domain anotherexample.com in
the programs and in SUMO articles. One day a person finds a security
hole in Firefox, buys the domain and make an attack site in order to
take over the computers that are led to that site through your locale.

It doesn't even have to be used as an attack in order to do harm, they
could choose to make a porn site at that domain. Even if a domain is
owned by a friendly person, you know know what will happen tomorrow. The
person could die or decide to sell the domain to someone not so friendly.

If you want to have a local example site, then why not contact the
administrator for you local top domain and ask the if they will make a
site for that purpose? I have a feeling that most of them would be
willing, if you mention that the address will be used by Mozilla in
Firefox, Thunderbird, and in support articles.

--
Kind Regards
Kim Ludvigsen


------------------------------

Message: 4
Date: Fri, 27 May 2016 08:46:06 +0200
From: "Francesco Lodolo [:flod]" <fl...@lodolo.net>
To: dev-...@lists.mozilla.org
Subject: Re: Don't translate example.* domains in error messages
Message-ID: <5b1096d7-fd5f-a942...@lodolo.net>
Content-Type: text/plain; charset=windows-1252; format=flowed

Il 26/05/16 22.05, Sebastian Hengst ha scritto:
> You can also use .example as top level domain to create partially
> localized domains, see the second page of
> https://tools.ietf.org/html/rfc2606 , e.g.
> <localized "example">.example
> For German, we used that for the email placeholder in the Firefox OS
> email app.
Sure it works, but I also have the feeling that we're missing a point
here (not referred to this reply specifically): "example.com" serves as
an example of a domain name.

"Hey, this address doesn't work. Check if you didn't write
*ww*.example.com instead of *www*.example.com".

Are we implying that the majority of Firefox users can't understand the
concept of "example.com" being a URL? Because they use plenty of .com
domain names, every day, that don't make any sense in their own language.

The only annoyance I see is when the spelling of "example" is so similar
to the word in your own language that it might look like a typo. But not
having references to potentially dangerous domains is far more important.

And, in my opinion, using "something.example" might be technically
acceptable, but potentially more confusing for users. Most of them are
familiar with .com and country TLDs, probably .net, but I doubt they get
".example" as part of a URL. And I say this from the point of view of
someone who had to explain for several years why his email address
didn't have a @yahoo.com or @hotmail.com (lately @gmail.com) at the end.

Francesco



------------------------------

Message: 5
Date: Fri, 27 May 2016 11:38:39 +0200
From: Philipp Kewisch <moz...@kewis.ch>
To: dev-...@lists.mozilla.org
Subject: Re: Localization feedback for date/time picker
Message-ID: <scCdncA4BaE9iNXK...@mozilla.org>
Content-Type: text/plain; charset=utf-8

Hi Tina,

some more feedback I've collected from mozilla.dev.apps.calendar:

On 5/26/16 9:00 PM, MakeMyDay wrote:
> Nice stuff. This is a HTML picker for an input element of type
> date/time, right?
>
> Not sure where to provide feedback, so here's what comes to mind:
>
>  * It probably would be an asset if the time picker would support
>    different levels of granulation for the minutes - e.g. 1 minute, 5
>    minutes and 15 minutes steps.
>  * The month picker doesn't provide the option to jump to the current
>    month by one click as we have it today. But this is just a nice to
>    have from my pow. The same is true for decorating the current day in
>    a month picker.
>
> Does that pickers work only while displaying a date/type related input
> field or is the month picker also intended to be exposed separately to
> make use it e.g. for minimonth?
>
> When will the picker be available?



------------------------------

Subject: Digest Footer

_______________________________________________
dev-l10n mailing list
dev-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-l10n


------------------------------

End of dev-l10n Digest, Vol 125, Issue 23
*****************************************