User talk:Hcatlin

I can't find these two messages, 'End' and 'Top' on the Wikipedia mobile site. Anybody know what type of message this is. Is it a link, where if you click on it you jump to the top or bottom? Or is it a message telling the reader that they are at the top or end?

Its supposed to be used in a future version of Palm Pre application. It is not currently live.

Do you know how these messages will be used when they do go live? If not, I'll just wait until it does go live. You will probably have guessed that the translation will be different depending on whether the message is used in a link or used to describe that you are at the end or top already; otherwise I wouldn't need to ask this question in the first place! If it turns out that the messages are to be used both in links and in place markers then I will be sunk (or lost for words:-)).

Are these messages now used? If so, how?

This component has been abandoned, and replaced by Special:Translate/out-wikipedia-mobile

Hi.

first, in case you are not the right person to ask this, i apologize. if by any chance you actually know who *is* the right person, i would be very grateful if you could indicate it.

continuing with the assumption you *are* the right person:

so we needed to add some mobile/handheld specific css on hebrew wikipedia, and it turns out we do not know exactly how to do it.

First, we added a new file: http://he.wikipedia.org/wiki/Mediawiki:Handheld.css Adding the file was not a problem, but it does not seem that the handheld devices actually load it.

the documentation for $wgHandheldStyle actually says that not all handhelds will load this file.

it seem that the only css loaded on hebrew wikipedia for mobiles/handhelds is: http://he.m.wikipedia.org/stylesheets/default.css

however, nobody in he wiki has the permissions required to edit this file. so:

• again, if you are not the right person to ask this - apologies
• if there is some magic incantation by which we can gain control over our handheld-css - we'll be thrilled to learn.
• failing that, could you please add the following to our css (whatever it mab be)?

.wpAbbreviation:after { content: " (" attr(title) ")"; }
abbr.wpAbbreviation { border: none;}

(these two lines will help us deal with "abbreviations", which behave differently, as the abbr actually rely on the tooltip, and many handhelds can't deal with tooltips).

peace, קיפודנחש 21:19, 26 June 2011 (UTC)

Opened up Bug 29634 to track this. Tfinc 20:49, 28 June 2011 (UTC)

Your recent commit broke translatewiki. Deleting nb.yml and zh-cn.yml fixed it. Please check your commits.

I'm confused. How do my mobile software commits end up here at translatewiki?

And what in a yml file can break?

They were not yaml, they were html.

Hello Hampton, please configure the mobile home pages for Upper Sorbian Wikipedia (hsb.m.wikipedia.org) and Lower Sorbian Wikipedia (dsb.m.wikipedia.org), see bugs 23281 and 23282.

Thank you in advance.

Hi, Can you help me regarding version of Urdu Wikipedia. Translations for [ur.m.wikipedia.org] were completed a couple of days ago. What should be done next to activate this.

Thanks, Omer

Hoi. every day we commit the localised messages to the Wikimedia Subversion. Every day the messages that are the same in English in both SVN and on the Wiki are selected by the LocalisationUpdate process. Thanks,

That's true for MediaWiki. Not for Translating:Wikimedia mobile.

I learned something .... the m in the url stands for mobile :)

We update the languages every 2-3 weeks. Depending.

A note here sure helps though! I'll do it whenever anything is really new. Its just a process I have to remember to start and push up manually.

Anyhow, http://ur.m.wikipedia.org/ is live!

Can do this for you - at least in git - if possible. If you'd want me to commit the updates, let me know.

This was completed a few days ago. I didn't see the message here.

Is MediaWiki:wmobile-nav_history basically referring to the same kind of history as the "history" tab on wikipages? --Purodha Blissenbach 23:42, 29 November 2009 (UTC)

No, "History" is browsing history or "Articles you have read before"

This is used in our application.

Could you please implant http://da.wikipedia.org/wiki/Forside_%28mobil%29 to http://da.m.wikipedia.org/ so it will get home page for the mobile version. I would also like to know if you know how to make http://da.m.wikipedia.org/ the default page when visiting http://da.wikipedia.org/ on mobile phones.

Thanks in advance

Regards,

http://pt.m.wikipedia.org/ seems to have the pt-br language translations. And http://pt-br.m.wikipedia.org/ does not exist. What can I do to get this fixed?

Has User:Hcatlin been contacted?

Siebrand moved the issue to Hcatlin's discussion page, but no response yet. Should I try contact in some other way?

The *articles* are in pt-br or the translations?

How is this setup of wikipedia proper? What is pt.wikipedia.org?

I mean, I didn't do anything special. pt.m.wikipedia.org should be scraping pt.wikipedia.org, and it should be loading the "pt" translation strings from this site.

But, I need much more info before I can figure this out.

Hi Hcatlin, sorry if I wasn't clear.

I was referring to the button names and the copyright and other messages at the bottom of the page, *not* to the articles.

In MediaWiki's interface, there are two variants of portuguese: Portuguese (pt) and Portuguese (Brazil) (pt-br). Users can set their MediaWiki interface language to the most appropriate.

In Wikipedia proper, there is a single Wikipedia for the portuguese language, so the articles are in a mix of pt and pt-br.

Now, it's not clear to me from pt.m.wikipedia.org how users would go about setting the interface language, but I guess it results from the URL they access.

If that is so, in principle, "pt" users (i.e. those who set their interface language in MediaWiki to "pt") should access pt.m.wikipedia.org and get the "pt" buttons and messages and the articles from pt.wikipedia.org.

The "pt-br" users should access pt-br.m.wikipedia.org and get the "pt-br" buttons and messages and the articles from the same pt.wikipedia.org.

If we direct users to the mobile version of wikipedia from within wikipedia itself, then users who have set their interface language to "pt" would be directed to pt.m.wikipedia.org and those that set their interface language to "pt-br" would be directed to pt-br.m.wikipedia.org. If we are unable to examine the interface language and direct users to the appropriate one, then both links should be presented: pt.m.wikipedia.org and pt-br.m.wikipedia.org and let users choose the appropriate one.

I have a similar pending issue like this with chinese languages. They share the same wikipedia and have different language selectors. Currently, the mobile site doesn't really think about an interface language... but I'm definitely willing to figure out a way to make that work well.

I think you are right... more subdomains makes it easier.

If you wouldn't mind opening a Bugzilla ticket stating what you just said, I'd really appreciate it. It does appear that you can tell what their UserLanguage is via javascript:

wgUserLanguage="pt-br", wgContentLanguage="pt",

bugzilla: 21806 created. Regarding how to figure out the UserLanguage, this functionality is already available in translatewiki.net through {{USERLANGUAGE}} (I believe it's implemented by one of the extensions there).

Does MediaWiki:wmobile-nav_history refer to the normal version history like the "history" tab on wiki pages? --Purodha Blissenbach 00:30, 4 December 2009 (UTC)

No, this is for the native application and is more like browser history.

Is MediaWiki:wmobile-nav_history identical with the "history" tab on usual wiki pages?

Its for the native iPhone application. Its not currently in use in other languages at the moment. It is a history of all of the pages that the *user* has viewed. more like a browser history.

Hi. Git doesn't show regular integration of translations. Could you start doing that more regularly? Thanks.

Its being done every time we push out a new version to the main site. Is that not regular enough?

The space before the question mark probably needs to be removed.