Difference between revisions of "User talk:Akozak"

From Creative Commons
Jump to: navigation, search
(Add languages to ODEPO)
(Add languages to ODEPO)
Line 26: Line 26:
 
::<tt><nowiki>}}</nowiki></tt>
 
::<tt><nowiki>}}</nowiki></tt>
 
::and then the contents of the other page are just: <code>Pt:ODEPO</code>. That should work. Sorry about that. [[User:Hamilton Abreu|Hamilton Abreu]] 03:36, 29 July 2010 (UTC)
 
::and then the contents of the other page are just: <code>Pt:ODEPO</code>. That should work. Sorry about that. [[User:Hamilton Abreu|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 <nowiki>{{Translations|{{:{{PAGENAME}}/Translations}}}}</nowiki> 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.

Revision as of 17:32, 30 July 2010

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:

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.