Closed Bug 831320 Opened 11 years ago Closed 11 years ago

[nl] Translate 2013 Firefox Flicks website

Categories

(Websites :: Firefox Flicks, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

References

Details

This bug is for the translation of the updated "Firefox Flicks" site for 2013.

The Firefox Flicks site is a video contest targetting talented filmmakers wishing to create fun videos about Mozilla and Firefox. This is the third iteration of this contest, the first contest was in 2006, the second contest was in 2012 and this year contest will focus on Mobile and Firefox OS promotion.

Here is the url on the development server:
https://firefoxflicks-dev.allizom.org/nl/

We are at stage one in which we announce the contest and make a call for participation to this contest.

The translation format for this project is .po files that you are on svn but also available through the Verbatim Web translation tool:

https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxflicks/locale/nl/LC_MESSAGES/messages.po
https://localize.mozilla.org/projects/firefoxflicks/

This is a 5750 words site but if you did the project last year, 3750 are reused, which means a translation of about 2000 words. Some of the strings similar to strings last year are also marked as fuzzy.

Please also note that there is one special string that is actually a set of about 20 strings that will nor be used in the site but will be inserted into a downloadable PDF for the Creative brief, this brief is actually a presentation with just a few words on each slide. In this special string, each slide change is indicated by an html line break (<br>) and if the same sentence is meant to be split in two slides, there will be an ellipsis indicating it, ex:

With Firefox OS, we're making smartphones more accessible...<br> ...while empowering more users in more ways.

This way we will be able to provide a localized Creative Brief and not just one in English.

if you can, please prioritize the translation of the brief over the other strings, this way our engagement team will be able to create the pdf's for your language while you are translating the rest of the site. We will of course provide you the pdfs so as that you can give feedback.

We are targetting a launch of the site with the announcement for January 22, there will also be further updates later this year to put the competing videos online and announce who the winners are.

Thanks!
Ton has already committed to SVN. I have made a few suggestions but I guess it’s ready to go ;-)
I really don't like the translation of mobile. I know it is the direct translation but it doesn't feel right. the problem is that i can't think of a better translation :-(
(In reply to Tim Maks van den Broek from comment #2)
> I really don't like the translation of mobile. I know it is the direct
> translation but it doesn't feel right. the problem is that i can't think of
> a better translation :-(

I second that, but also have nothing better to offer. Maybe it’s just the choice of the original word ‘mobile’ that’s a pain, and we just go along with it.
By the way, several of my suggestions concern the translation of Award, which IMHO should be ‘prijs’ rather than ‘toekenning’. Open for debate obviously.
(In reply to Pascal Chevrel:pascalc from comment #0)
> 
> if you can, please prioritize the translation of the brief over the other
> strings, this way our engagement team will be able to create the pdf's for
> your language while you are translating the rest of the site. We will of
> course provide you the pdfs so as that you can give feedback.

Pascal, could you or make the team provide one? And does it allow real ellipsis characters instead of 3 dots (as we normally use those for nl)?

(In reply to Tim Maks van den Broek from comment #2)
> 
> I really don't like the translation of mobile. I know it is the direct
> translation but it doesn't feel right. the problem is that i can't think of
> a better translation :-(

It’s not the word ‘mobile’ that worries me, but rather ‘getting mobilized’. Is this what you’re pointing at, or could you point out where ‘mobile’ worries you?

Even though we know about ‘mobiliseren’, I guess ‘getting mobilized’ is more like a word play / pun Mozilla is using than ‘gemobiliseerd raken/worden’ as we use it for e.g. army purposes. (Stimuleren tot) in beweging komen / aanzetten tot / inzetten / in het werk stellen doesn’t feel right either, so unless there’s something better for it (?), I’d stick to ‘mobiel worden’.

Some suggestions and nits have been implemented, more nits to follow. Btw, ‘toekenning’ was used on purpose to distinguish new from older strings for the first view.
(In reply to Ton from comment #5)
> (In reply to Pascal Chevrel:pascalc from comment #0)
> > 
> > if you can, please prioritize the translation of the brief over the other
> > strings, this way our engagement team will be able to create the pdf's for
> > your language while you are translating the rest of the site. We will of
> > course provide you the pdfs so as that you can give feedback.
> 
> Pascal, could you or make the team provide one? And does it allow real
> ellipsis characters instead of 3 dots (as we normally use those for nl)?

Yes you can use real ellipsis in your translation

R1 went live yesterday, so closing this bug, the generation of the pdf by engagement is a separate issue :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.