Difference between revisions of "User talk:Akozak"

Thanks for your work on the CClearn pages; you might make yourself a user page with a bit of information about who you are, so people can connect this account to any other efforts you've done elsewhere. You can see mine (linked to my name) as a (rather simple) model. Thanks! JesseWeinstein 03:02, 10 June 2009 (UTC)

Add languages to ODEPO

Hi Akozak, if you could you add the following at the top of page ODEPO:

{{Translations:
  {{ODEPO/Translations}}
}}

Then create the new page ODEPO/Translations with contents:

articles=Pt:ODEPO

and leave that new page unprotected (the protection of page ODEPO cannot be cascading), then translators could add their translated pages without a need to request the addition to admins every time. If this seems workable, could you please also add something similar to:

• OER Resources
  • OER Resources/Translations Contents: articles=Pt:Recursos Sobre OER Pt:Recursos OER
• Creative Commons and Open Educational Resources
  • Creative Commons and Open Educational Resources/Translations Contents: articles=Pt:A Creative Commons e os Recursos Educativos Abertos

These two will become red-linked, but I'll work on them next. Let me know. Thanks. Hamilton Abreu 15:37, 27 July 2010 (UTC)

The thing about putting it in the Protected template, is that the languages will then appear at the bottom of the page, next to the message about protection. Well, we should really have it in the same place in all pages. I've been putting it at the top of all pages, following the apparent existing convention. Of course, we could change all of them to the bottom. We could also move the call to {{Protected}} to the top of the page. But it would be important for usability to have it always in the same position of all pages. What do you think? Hamilton Abreu 02:42, 29 July 2010 (UTC)

(Later edit) Hmm, I made a mistake above. It should read:

{{Translations|

  articles={{:ODEPO/Translations}}

}}

and then the contents of the other page are just: Pt:ODEPO. That should work. Sorry about that. Hamilton Abreu 03:36, 29 July 2010 (UTC)

I don't think I want to put it at the top of the database landing pages for design reasons (I'm not currently very happy with the Translations template design) since I spend quite a bit of time tweaking those layouts. But maybe it makes sense for "content" pages that are quite long.

In any case, it isn't working. I've added {{Translations|{{:{{PAGENAME}}/Translations}}}} to ODEPO and it still gets put into Untranslated even though there is content on the sub-page adding it to a language. I'll probably need to dig in to the Translations template to figure it out.

For it to work, "articles=" needs to be moved from the subpage to the ODEPO page (check my message three paragraphs above). Hamilton Abreu 22:33, 30 July 2010 (UTC)

Akozak, there's one more page which is protected and needs the translations template. So, the current list is:

• OER Translation: Pt:OER
• OER Resources Translation: Pt:Recursos Sobre OER
• ODEPO Translation: Pt:ODEPO
• Creative Commons and Open Educational Resources Translation: Pt:A Creative Commons e os Recursos Educativos Abertos

Thanks Hamilton Abreu 00:03, 3 August 2010 (UTC)

Done! Each of those pages has a /Translations page now. Thanks for all your work and thanks for reporting the issue. Akozak 21:23, 3 August 2010 (UTC)

Me again. Could we do the same to FFAQ? Hamilton Abreu 21:01, 14 August 2010 (UTC)

Placement of translations

Hi Akozak, me bothering you again. Sorry about this, but I have the feeling that I'm placing the translations template where you don't want it to be. Initially I was placing it at the bottom of pages, but then found a few instances where it already was at the top. So, I moved it to the top of all pages. Then you placed it within another template where it comes somewhere in the middle of the page but, lately, I get the feeling you'd prefer it at the bottom. So, here I am :)

I can place it wherever it is preferred, no problem at all. I'd just ask you one thing: having some experience of this, CC Wiki would gain in usability, from it being always at the same place of all pages. This is because these MediaWiki wikis are always faking to be multilingual, but they are nothing of the sort; if your language is not English, you're always shifting between English and non-English pages. For example, clicking the logo always takes you to the English main page, irrespective of your language.

So, before a user even enters a page, they should know where in that page they will be able to find the translation links. The template can be either at the top or bottom (although at the top, avoids having to scroll the page), as long as it's always in the same place of all pages. Would you agree with this?

If you agree, let me know, top or bottom, and I'll move it there in all pages. If you don't, let me know how to proceed. Hamilton Abreu 02:10, 10 August 2010 (UTC)

Yes, I apologize for the inconsistency. I'm rather picky when it comes to the layout of pages, and unlike Wikipedia or other wikis, we use MediaWiki for a variety of uses. So it isn't easy for us to adopt a standard page layout.

I agree we should try to be consistent, so for now let's go with the top of the page for most pages and for just a few "landing pages" (such as OER, Translate, the Main Page) we leave it at the bottom. Does that sounds sane?

Thanks for your work, I really do appreciate it. Perhaps you can help me revisit this question soon when we start discussing a re-skin of the wiki in Vector. Akozak 17:13, 10 August 2010 (UTC)

That sounds sane and workable. And yes, glad to revisit it for Vector.

Incidentally, you may have also noticed I used the template not just for articles in the main namespace, but for everything else translated (templates, categories, images). I later figured out that properties aren't enabled for those other namespaces. The effect is one only: on the translated pages of those other namespaces, we only get a link to the English page; no links to the other translated pages, because the Has translations: property of the English page doesn't work. What are your thoughts on this, if any? Would it cause any problems if properties were enabled for all (at least, all the standard) namespaces? Not something where you want to spend energy for now?

Thanks. Hamilton Abreu 19:08, 10 August 2010 (UTC)

This is a fairly complex issue which I've thought about before. I'll put it in my queue to look at and get back to you. Akozak 20:44, 10 August 2010 (UTC)

Missed one

When you were reverting the latest spammer, Special:DeletedContributions/Dillingerforce, you missed the user page. I've caught it; just wanted to let you know. JesseWeinstein 07:15, 13 August 2010 (UTC)

Thank you! Akozak 16:52, 13 August 2010 (UTC)