<div dir="auto"><div>We need to go through that CSV and identify what terminological metadata is relevant to us first, but once we do, I'll happily share it with you and Michele.<div dir="auto"><br></div><div dir="auto">Flod is in touch with both Michele and the Photon team to represent l10n for Firefox.</div><div dir="auto"><br></div><div dir="auto">Jeff</div><br><div class="gmail_extra"><br><div class="gmail_quote">El 6 feb. 2017 21:59, "Bram Pitoyo" <<a href="mailto:bram@mozilla.com">bram@mozilla.com</a>> escribió:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="quoted-text"><div>Jeff wrote:<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">We've taken the liberty of extracting a large set of English terms from
mozilla-aurora in a csv file. It would be great to have time with UX to
review those terms, determine which terms need specific details to
clarify their usage/message within the product and which terms we don't
need.</blockquote><div><br></div></div><div>If you have a link to the CSV, I can help you get in touch with Michelle Heubusch, our content strategist. I’m working together with her on unifying error pages messaging.<br><br></div><div>It would also be interesting for the Photon UX designers to have a look at the strings collection. I know that they’ve been working on a guideline for the tone of voice of the product (what does our UI sound like?). It would be good to integrate l10n early in this process, especially as our messaging get less technical and more context-sensitive.<br></div></div><div class="elided-text"><div class="gmail_extra"><br><div class="gmail_quote">On 7 February 2017 at 09:41, Jeff Beatty <span dir="ltr"><<a href="mailto:jbeatty@mozilla.com" target="_blank">jbeatty@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Thanks for adding l10n to this discussion. I want to be sure that everyone knows that we're aware of the brittle nature of the l10n infrastructure in Firefox and we're actively working to fix that. Zibi is in talks with Quantum folks to solve the Quantum l10n story, flod is working with the Firefox and release management team to manage strings during the train schedule, and Axel is working on a more continuous form of localization that will enable us to make changes across branches much more easily, leading to more flexibility for these types of experiments.<br><br></div>One thing that can help improve the messaging consistency across languages is for us (l10n) and the UX team to define out concepts, assign terms and definitions to those concepts, and make that information available to localizers to inform their decisions about how to translate something. Our translation tools can/will consume and retrieve this terminological data and present it to the localizer to translate more accurately. This applies not only to the private browsing messaging, but the messaging for all Firefox features & modules.<br><br></div>We've taken the liberty of extracting a large set of English terms from mozilla-aurora in a csv file. It would be great to have time with UX to review those terms, determine which terms need specific details to clarify their usage/message within the product and which terms we don't need.<br><br></div>Thanks,<br></div>Jeff<br></div><div class="gmail_extra"><div><div class="m_-7247252254721715209h5"><br><div class="gmail_quote">On Mon, Feb 6, 2017 at 1:31 PM, Justin Dolske <span dir="ltr"><<a href="mailto:dolske@mozilla.com" target="_blank">dolske@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I'd also add that one of the big challenges of testing localization changes is the time and effort involved. Typically these tests are done very rapidly (sometimes within a few days), which is pretty disjoint from the normal train-based L10N process where changes can take up to 18 weeks. So when the assumption is that things involving localized strings are difficult, slow, and/or require special coordination, it just doesn't happen.<br><br></div>Justin<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 6, 2017 at 10:16 AM, Peter Dolanjski <span dir="ltr"><<a href="mailto:pdolanjski@mozilla.com" target="_blank">pdolanjski@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401m_-9111740229727602636gmail-im">On Fri, Feb 03, 2017 at 12:28:30PM -0500, Peter Dolanjski wrote:<br>
> We are planning a number of upcoming studies (some through heartbeat<br>
> surveys, others through Shield) to dig into privacy positioning/messaging<br>
> to better understand users' perceptions in this area.<br>
> As part of this, we plan to explore messaging around tracking protection,<br>
> private browsing, etc.<br>
> These plans are still in the formation stage, but we hope to be able to get<br>
> to some initial learnings quite quickly at which point, we can share the<br>
> results.<br>
<br>
</span>This brings an interesting problem: localization. The way localization<br>
works AIUI is that we write strings in English, and those strings are<br>
translated in various languages.<br>
<br>
But different languages are used by people with different cultures, and<br>
while some wording tweaks in English can have an impact on perception<br>
wrt privacy, tracking protection, etc. they might also have the opposite<br>
effect when translated to another language...<br>
<br>
Do we look at these things?<span></span></blockquote><div><br></div></span><div>For such studies, we have to start somewhere, so we tend to start with one language and see what patterns exist. That'll give us potential areas to focus on for further exploration/design work.<br></div><div>I would like to explore differences between key markets, though, so we'll try to strike a balance between going wide and getting results without long cycle times.<br><br></div><div>That said, you've absolutely highlighted a key challenge we face with areas of the product where they may be significant differences in perception. I hope we can get better at understanding these differences, starting with strategic markets.<span class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401HOEnZb"><font color="#888888"><br><br></font></span></div><span class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401HOEnZb"><font color="#888888"><div>Peter <br></div></font></span></div><div class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401HOEnZb"><div class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 6:47 PM, Mike Hommey <span dir="ltr"><<a href="mailto:mh@glandium.org" target="_blank">mh@glandium.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Fri, Feb 03, 2017 at 12:28:30PM -0500, Peter Dolanjski wrote:<br>
> We are planning a number of upcoming studies (some through heartbeat<br>
> surveys, others through Shield) to dig into privacy positioning/messaging<br>
> to better understand users' perceptions in this area.<br>
> As part of this, we plan to explore messaging around tracking protection,<br>
> private browsing, etc.<br>
> These plans are still in the formation stage, but we hope to be able to get<br>
> to some initial learnings quite quickly at which point, we can share the<br>
> results.<br>
<br>
</span>This brings an interesting problem: localization. The way localization<br>
works AIUI is that we write strings in English, and those strings are<br>
translated in various languages.<br>
<br>
But different languages are used by people with different cultures, and<br>
while some wording tweaks in English can have an impact on perception<br>
wrt privacy, tracking protection, etc. they might also have the opposite<br>
effect when translated to another language...<br>
<br>
Do we look at these things?<br>
<span class="m_-7247252254721715209m_8821602798836843282m_-9040845596166160401m_-9111740229727602636HOEnZb"><font color="#888888"><br>
Mike<br>
</font></span></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div><span class="m_-7247252254721715209HOEnZb"><font color="#888888">-- <br><div class="m_-7247252254721715209m_8821602798836843282gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks,<br></div>Jeff<br></div></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a><br>
<br></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div>