Closed
Bug 376277
Opened 18 years ago
Closed 18 years ago
Update Google snippets with corrected links
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pascalc, Assigned: reed)
Details
Attachments
(2 files, 1 obsolete file)
Here is a diff correcting links on google snippets to use long locale names and not short locale names
Reed, it's the first time I provide a diff to be applied on the CVS, if it's not correctly done, tell me.
| Reporter | ||
Comment 1•18 years ago
|
||
Here is an archive with updated snippets, please replace the old snippets with those.
Attachment #260369 -
Attachment is obsolete: true
Reed: I know you're slammed with Thunderbird 2 stuff. Think you can get to this by the end of this week?
| Assignee | ||
Updated•18 years ago
|
Assignee: nobody → reed
Any progress on this, Reed? Should we wait till you are available after you get done with classes? (This is fine, just let me know)
| Assignee | ||
Comment 4•18 years ago
|
||
(In reply to comment #3)
> Any progress on this, Reed? Should we wait till you are available after you get
> done with classes? (This is fine, just let me know)
Can it wait, please? This requires some thought on my part, and I just don't have the time for that currently.
| Assignee | ||
Comment 6•18 years ago
|
||
(In reply to comment #5)
> Of course -- when do you think you could look at this again?
At least a week from today. I can try to do something this weekend, but no promises... If it's really top priority, I'll see if I can fit it in. I might just commit it as-is and do my modifications later, if you think that would be ok.
Yes go ahead and commit now.
These still aren't being processed live anyway, and we can then have Google check the links for accuracy with their scripts.
| Assignee | ||
Updated•18 years ago
|
Status: NEW → ASSIGNED
Summary: fix links for fy-NL and sv-SE on google snippets → Update Google snippets with corrected links
| Assignee | ||
Comment 8•18 years ago
|
||
Committed. I'll eventually work on this, but it's committed as-is for now.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 9•18 years ago
|
||
The snippets displayed for the /{locale}/ folder is not the right one, it is the one from /{locale}-1.0/, my fault for not noticing it.
Here is a zip archive containing all the /{locale}/ folders with the right sentence ("Thanks for choosing Firefox, the easy-to-use Web browser from Mozilla. Find out more about us.")
One last thing, I think I mentionned that in the past but the /zh/ folders is a copy of the /zh-TW/, I don't know if it shouldn't be a copy of the /zh-CN/ folder instead as I don't know which population is seeing the snippets from the /zh/ folder.
Comment 10•18 years ago
|
||
Reed: can you commit again please?
Gen: can we get an opinion from you on the /zh/ stuff?
Comment 11•18 years ago
|
||
Bob- can I ask you to please check the "snippets" - these are the little comments on the Firefox start/search page, to make sure that traditional Chinese is properly shown?
Comment 12•18 years ago
|
||
I will also ask Zhiyong at Mozilla China to check for us.
Comment 13•18 years ago
|
||
Gen: the snippets of zh-tw part in Pascal's package are properly shown.
Pascal: mozilla.com might have httpd log to know which population is seeing the snippets from /zh/? IMO we could just remove the folder, or leave as it.
Comment 14•18 years ago
|
||
All: it looks like we're ok based on a report I just got from Google. I've confirmed that Firefox users in China are seeing snippets from www.mozilla.org/start-snippets/zh-cn/ and users from Taiwan are seeing snippets from www.mozilla.org/start-snippets/zh-tw/.
Reed: can you please commit Pascal's updates today?
| Assignee | ||
Comment 15•18 years ago
|
||
Done.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Product: mozilla.org → Websites
Updated•13 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•