421969 - lots of out-of-date copyright info on the trunk

Status: RESOLVED WONTFIX

(Mozilla Localizations :: Other, defect)

Description

[chris hofmann]

Attachment: 2006 and 2007 copyright's from scan of .dtd files under ./l10n

we should get all these fixed (maybe with one sweep of the tree), then make the trunk sweep again after the first of every year.   

other suggestions have been made to try and get copyright date(s) in one central location so each localization team doesn't have to remember to keep this info up to date.  see bug 414939

Comment 1

[chris hofmann]

Attachment: just the firefox ab-CD/browser/chrome .dtd's with the string matching 200[4567]

Comment 2

[Phil Ringnalda (:philor)]

If you really want to fix this, rather than looking at a lot of random numbers, you'll want to look at the actual strings (especially if you want the ones with non-Arabic numerals).

There are four strings you want to look at: copyrightInfo (copyrightText, for people desperately far behind who probably won't ship) in browser/chrome/browser/aboutDialog.dtd, copyright.years in browser/locales/en-US/chrome/help/platformStrings.dtd (extra fun because not everyone's actually using it like they should), about.copy.beforeLink in toolkit/chrome/global/about.dtd, and the string in toolkit/locales/en-US/chrome/mozapps/help/welcome.xhtml.

So:

http://mxr.mozilla.org/l10n/search?string=copyrightInfo&find=%2Fbrowser%2F is the likely-to-succeed locales, all 2008 with the possible exception of pa-IN where I don't know whether ੮ is an eight or not.

http://mxr.mozilla.org/l10n/search?string=copyrightText&find=%2Fbrowser%2F is the not-looking-good locales, which haven't matched a change from January 25th yet, all not-2008 but also including two more where you can't just change it for them, since you don't know their numerals.

http://mxr.mozilla.org/l10n/search?string=ENTITY+copyright.years&find=%2Fbrowser%2F is the string that *should* appear in Help, a mix of 2007 and 2008

http://mxr.mozilla.org/l10n/search?string=2003-&find=firefox_welcome.xhtml is a stab at finding the locales that missed spotting the change to using &copyright.years; in help content, though someone more thorough than me would check all the help files, and it misses anyone using different numerals.

and finally, http://mxr.mozilla.org/l10n/search?string=2003-&find=%2Fwelcome.xhtml is the trap for the unwary, the one page of help content that doesn't use an entity, with a mix of (fewer) 2008, 2007, and back to the dawn of time.

Personally, my approach to fixing it would be to cc the accounts that localizers watch to a bug with those links in it, give it a few days, and then file bugs on the locales that look like they are going to ship.

Comment 3

[Francesco Lodolo [:flod]]

Does make it sense considering the help files since they're moving to SUMO?

Comment 4

[Axel Hecht [:Pike]]

I'd ignore the help files.

Comment 5

[Rimas Kudelis [use needinfo to ping]]

(In reply to comment #2)
> http://mxr.mozilla.org/l10n/search?string=copyrightInfo&find=%2Fbrowser%2F is
> the likely-to-succeed locales, all 2008 with the possible exception of pa-IN
> where I don't know whether ੮ is an eight or not.

੮ is U+0A6E GURMUKHI DIGIT EIGHT, so pa-IN is OK, I guess.

Comment 6

[João Neves]

There are some fake copyright issues, particular in calendar. I've just commited a fix for the 2 detected issues for pt-PT.

Comment 7

[chris hofmann]

Thanks João!

Comment 8

[David Tenser [:djst]]

(In reply to comment #3)
> Does make it sense considering the help files since they're moving to SUMO?
> 

I second Axel's suggestion to ignore the help files, as those are already imported to SUMO.

Comment 9

[Marcelo Poli]

A great number of issues come from lines like this

   - Portions created by the Initial Developer are Copyright (C) 2006

Those lines are comments and they are part of the license.
en-US have the same year on those lines.

Comment 10

[Gordon P. Hemsley [:GPHemsley]]

It doesn't appear that any modern code keeps years in localizable strings. The locales that still have the old strings probably are not going to be updated any time soon, so resolving this as WONTFIX.