Umm what the link actually says is this: "This is recommended in the following scenarios: - You translate only the template of your page, such as the navigation and footer, and keep the bulk of your content in a single language. This is common on pages that feature user-generated content. - Your page targets users in multiple regions (for example, en-us, en-uk, and en-ie), but each regional version differs only in small details, such as the currency used."
Neither of these are true; the entire contents of the whole page are different (therefore the first scenario does not apply), and Simplified vs. Traditional is a non-trivial difference not at all analogous to "small details such as the currency used" (therefore the second scenario does not apply either). How sad that the first answer here is a "Not our problem :-)!"... 2011/10/17 Daniel Friesen <[email protected]> > See this: > https://www.google.com/support/webmasters/bin/answer.py?answer=189077 > > These variants are automatic conversions so the variant-neutral version is > in fact the canonical version of the page. Even though it's in a different > script it is the same text. > > Essentially all the variants point to the variant neutral form with > canonical links. And the canonical page includes rel=alternate forms for > each of the variants including a hreflang on the <link>. > > In search engines like Google and perhaps any others that decide to > implement this as well it allows the search engine to know what the > canonical is and understand what other languages or variants a page is > available in. When provided with this information the search engine can > give a user using the search engine a link in their own language instead > of the canonical link. In other words, if Google has separate support for > say zh-tw and zh-hk and then for the same search result Google can send a > user who uses zh-tw to our zh-tw variant and a user who users zh-hk to our > zh-hk variant. All with the same search ranking and results for the page. > > The only shame is that each lang requires a rel=alternative and we support > a pile of languages. If it wouldn't require hundreds of lines inside the > head I would've liked to add support for an improved persistent uselang. > Then Google would be nice enough to send users browsing google.de who > follow an en.wp link to a page that has a German user interface. > > > So the bug here is in Facebook ignoring what the user inputed and > canonicalizing the url instead of either keeping the url (but using the > canonical to group it into one opengraph item) or implementing support for > rel=alternate's with other hreflang's and providing users who use > different variants of zh with different urls. > > -- > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] > > On Sat, 15 Oct 2011 21:30:08 -0700, Liangent <[email protected]> wrote: > > I guess it's because we have <link rel="canonical" > > href="http://zh.wikipedia.org/wiki/Gmail"; /> in page source, so > > Facebook is fetching the canonical (variant-neutral) version (and this > > is expected, since http://zh.wikipedia.org/zh-tw/Gmail and > > http://zh.wikipedia.org/zh-cn/Gmail refer to the same article), where > > zh is used as the interface language. However zh falls back to > > zh-hans, so all interface messages are in zh-hans. > > > > -Liangent > > > > On Sun, Oct 16, 2011 at 10:49 AM, <[email protected]> wrote: > >> Gentlemen, no matter if in Google search results, or Facebook link > >> previews, links that specifically have the zh-tw part in them > >> http://zh.wikipedia.org/zh-tw/ ... > >> still end up having simplified Chinese, despite no such simplified > >> <title> > >> appearing in the entire page. > >> I suspect somehow the simplified Chinese version is considered Cache > >> Equivalent for <title> purposes ... but it is not and looks horrible to > >> me trying to present a fully Traditional appearing link. > >> Go ahead and test, share "http://zh.wikipedia.org/zh-tw/Gmail"; via > >> Facebook, and notice the simplified Chinese there in the title of the > >> link created. > >> > >> _______________________________________________ > >> Wikitech-l mailing list > >> [email protected] > >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
