852137 - [tracking][l10n] 15 Years Contribute Page Changes

Status: RESOLVED FIXED

(www.mozilla.org :: L10N, defect, P1)

Description

[Brian King [:kinger]]

This is a tracking bug to monitor the changes needed on the contribute page for en-US and the locales for the 15th anniversary campaign.

Locales: EN, ES, PT-BR, FR, DE, ID, NL, ZH-TW

Comment 1

[Pascal Chevrel:pascalc (PTO until April 26)]

Since we will have different content for this set of locales than from other locales currently translating the page and since this is temporary content, I woud propose to add for these locales only an extra lang file and put conditionnal content depending on the locale in the template itself. I can do that but if I am not available, mozilla.org webdev people can help too.

Comment 2

[Brian King [:kinger]]

Sounds good, once we don't rule out other locales wanting to opt-in as well.

Comment 3

[Jennifer Bertsch [:jbertsch]]

Hi Pascal-

I'm a little confused on process on this one :)

Has your team started translating the final text?

Or are you waiting for the strings in bedrock?

What is your time frame?  My best guess is that our launch date is March 28 in the AM (morning in Europe or morning in the US?  I don't know). 

I'll be in MV tomorrow sitting next to Chris More if you want to discuss in person.

Thanks so much,
Jen

Comment 4

[Jennifer Bertsch [:jbertsch]]

Attachment: moz15 contribute slideshow mock up

Comment 5

[Jennifer Bertsch [:jbertsch]]

Hi Pascal-

It was great to meet up with you this morning.

The final copy for the contribute page is here:
https://etherpad.mozilla.org/GF41iX18ul

I am attaching a screenshot of how we expect the text to be used in a slideshow on the contribute page.

Can we begin L10N without having the strings coded?  Craig:  what is your target date to have the strings coded?

I will ask Tara to provide any additional text that might need L10N (social, etc).

Thanks for your help,
Jen

Comment 6

[Craig Cook (:craigcook)]

I can get the strings marked up by tomorrow (20 March), at least enough for extraction, but we won't have a testable page for a few more days. I'm hoping to have at least some rough prototype on a demo server by Friday (22 March) if all goes well.

Comment 7

[Tara (musingt)]

Thanks all!  quick comment from me:

* If we can prioritize the translation of the header: "15 years of a better Web" that would be great as that will help us localize the stamp/mark that's in the top left of the page and will be used across other channels. 

* Also, the "v2" of fact number 15 is likely not going to be needed.  It was produced for social media but I don't think that's the official string that they are usuing.  So I would de-prioritize, if not move it entirely, from the l10n list. Social channels (email, twitter, facebook, snippet) are being led by user engagement so they should be following up on l10n needs directly.

Comment 8

[Pascal Chevrel:pascalc (PTO until April 26)]

(In reply to jbertsch from comment #5)
> Hi Pascal-
> 
> It was great to meet up with you this morning.
> 
> The final copy for the contribute page is here:
> https://etherpad.mozilla.org/GF41iX18ul
> 
> I am attaching a screenshot of how we expect the text to be used in a
> slideshow on the contribute page.
> 
> Can we begin L10N without having the strings coded?  Craig:  what is your
> target date to have the strings coded?
> 
> I will ask Tara to provide any additional text that might need L10N (social,
> etc).
> 
> Thanks for your help,
> Jen

Thanks Jen, the screenshot realy helps understanding what is requested. yes, I can put the strings for translation now that I have the contexte and Craig will just have to copy/paste them from the lang file to make sure we use the same strings.

Comment 9

[Pascal Chevrel:pascalc (PTO until April 26)]

(In reply to Tara (musingt) from comment #7)
>  Social channels (email, twitter, facebook, snippet) are being
> led by user engagement so they should be following up on l10n needs directly.

Do you mean that they will contact my team separately? (They haven't so far)

Comment 10

[Tara (musingt)]

Yes, I am not clear on the l10n needs for those other channels, so I have asked that they work with you directly on that.

Comment 11

[Pascal Chevrel:pascalc (PTO until April 26)]

I have created the strings resource for this project (mozorg/15years.lang). Note that I detected a styling problem  and added markup to the title that way:

<strong>15 years</strong> of Mozilla

The screenshot shows that we need to split the sentence for design purposes (for the record, that's to avoid such problems that we need strings in the template first).

Comment 12

[Craig Cook (:craigcook)]

(In reply to Pascal Chevrel:pascalc from comment #11)
> I have created the strings resource for this project (mozorg/15years.lang).
> Note that I detected a styling problem  and added markup to the title that
> way:
> 
> <strong>15 years</strong> of Mozilla
> 
> The screenshot shows that we need to split the sentence for design purposes
> (for the record, that's to avoid such problems that we need strings in the
> template first).

I spotted that, too, but even moreso that particular design isn't going to be practical once it's rendered in live text and CSS. Any variation in the typography or number of characters will break the layout when it's in such a tight formation. I talked to Lee about the problems with the design and we're working on a different header that will be more l10n friendly, maybe just a big "15" in the circle and a regular text headline above the intro. The text can still be heavily styled, it just needs room to reflow when needed.

Even so, we should keep your markup since it gives us more styling options. If I hit anything else in the implementation that needs any special formatting or splitting strings I'll let you know ASAP.

The rest of the slides are just plain blocks of text, and my only concern there is making sure we have room to accommodate reflow for varying lengths. As long as there's enough room in each block for an extra line or two of text we should be fine.

Comment 13

[Brian King [:kinger]]

Hi All,

Just a reminder that this is a tracking bug! You may want to use bug 852190 to discuss implementation or file new bugs and make them block this.

Comment 14

[Kohei Yoshino [:kohei]]

All dependencies have been resolved.