Talk:Activity Template: Difference between revisions
(New page: We should have an obvious place to grab the .xo bundle from for installation onto the laptop. --~~~~) |
(translations + obxes) |
||
| Line 1: | Line 1: | ||
== .xo bundle == |
|||
We should have an obvious place to grab the .xo bundle from for installation onto the laptop. --[[User:Walter|Walter]] 12:11, 12 October 2007 (EDT) |
We should have an obvious place to grab the .xo bundle from for installation onto the laptop. --[[User:Walter|Walter]] 12:11, 12 October 2007 (EDT) |
||
: There's the {{tl|OBX xobundle}} that can used. --[[User:Xavi|Xavi]] 14:11, 12 October 2007 (EDT) |
|||
== OBXes & translations == |
|||
These two concepts are very hard to combine and manage. Even if you decide to create translated versions for each [[OBX]], the biggest problem will be keeping the data they use and reference synchronized (ie: links to .xo, .pot, team members, etc). My personal take is to not include the [[OBX]]es in the translated pages, but I feel like cheating on non-english readers. |
|||
A possible alternative is to factor out things and let them be reused by transclusion — either the actual data used by the [[OBX]]es (ie: strings, links, etc) or the full olpcbox-set into a sub-page that can be transcluded as an autonomous unit. Using sub-pages for each piece of data is overkill and error prone (as you are sort of trying to simulate a hierarchical database based on wiki-pages). A single page that only has the olpcboxes for an activity ensures that all translations are in sync. --[[User:Xavi|Xavi]] 14:11, 12 October 2007 (EDT) |
|||
Latest revision as of 18:11, 12 October 2007
.xo bundle
We should have an obvious place to grab the .xo bundle from for installation onto the laptop. --Walter 12:11, 12 October 2007 (EDT)
- There's the {{OBX xobundle}} that can used. --Xavi 14:11, 12 October 2007 (EDT)
OBXes & translations
These two concepts are very hard to combine and manage. Even if you decide to create translated versions for each OBX, the biggest problem will be keeping the data they use and reference synchronized (ie: links to .xo, .pot, team members, etc). My personal take is to not include the OBXes in the translated pages, but I feel like cheating on non-english readers.
A possible alternative is to factor out things and let them be reused by transclusion — either the actual data used by the OBXes (ie: strings, links, etc) or the full olpcbox-set into a sub-page that can be transcluded as an autonomous unit. Using sub-pages for each piece of data is overkill and error prone (as you are sort of trying to simulate a hierarchical database based on wiki-pages). A single page that only has the olpcboxes for an activity ensures that all translations are in sync. --Xavi 14:11, 12 October 2007 (EDT)