From Apache OpenOffice Wiki
Jump to: navigation, search
(10:02:23) bettina-h: Hi Stefan good morning. According the last minutes you are taking the minutes today, right?
(10:03:32) stx12: oops
(10:04:17) stx12: I knew that there would be something unexpected...
(10:04:28) bettina-h: :)
(10:05:16) b_osi_away est désormais connu sous le nom de bosi
(10:05:37) mdamboldt [n=md97092@sd-socks-197.staroffice.de] a rejoint le salon.
(10:05:43) mdamboldt: Sorry for beeing late.
(10:05:51) stx12: so, let's see who is here...
(10:05:56) rtimm [n=Ruediger@sd-socks-197.staroffice.de] a rejoint le salon.
(10:06:02) lgodard: hi all
(10:06:12) lgodard: sorry, i'm booked :(
(10:06:36) stx12: bettina-h, bosi, mdamboldt
(10:06:59) stx12: anybody else participating in the meeting?
(10:08:12) ***rtimm is listening ...
(10:08:27) stx12: then let me quickly go through the AIs:
(10:08:31) stx12: 2008_04_10_1: Ask Stella about putting the new branding from www.openoffice.org onto the extension site; Most important would be the banner on top.
(10:08:36) stx12: mdamboldt?
(10:08:38) mdamboldt: Stella is in progress to create some drafts. Expect an url pointing to such drafts later today or by tomorrow. I will announce it on the mailing list.
(10:08:58) stx12: good; this is making progress...
(10:09:10) stx12: 2008_04_10_2: What process to translate an extension itself
(10:09:21) stx12: lgodard: is not available...
(10:09:23) lgodard: no progress
(10:09:32) _Nesshof_: not that true at all
(10:09:34) lgodard: i ty to follow this dioscussion
(10:09:50) _Nesshof_: at least for the extensions already in the repository
(10:10:06) lgodard: _Nesshof_: there are two targets
(10:10:07) _Nesshof_: we will have from 3.0 codeline on extension only modules
(10:10:24) _Nesshof_: so that a separation of extension code in pootle is doable
(10:10:53) lgodard: what about extension that are not in the cvs ?
(10:11:19) _Nesshof_: I only can take care about stuff which is present somehow
(10:11:48) lgodard: _Nesshof_: wa have to provide tools btw for extensions writers
(10:12:05) lgodard: that can scale when going in the cvs
(10:12:09) _Nesshof_: lgodard: what kind of tools for which purpose ?
(10:12:33) lgodard: _Nesshof_: have a defined methodology for translating an extension
(10:12:43) lgodard: a common way of doing it
(10:13:08) lgodard: but, that is the goal of this AI. datail it.
(10:13:10) _Nesshof_: my first approach would be to use the same tools as we use for OOO
(10:13:10) lgodard: detail
(10:13:13) stx12: is there a desciption of the translation workflow (via pootle) for extension developers to look at?
(10:13:44) lgodard: _Nesshof_: not that sure, but why not
(10:13:58) _Nesshof_: stx12: I would guess that there is also no description for OOo code available
(10:14:17) _Nesshof_: looks like a new action item
(10:14:20) stx12: _Nesshof_: so the answer is "no"
(10:14:37) stx12: who is taking this?
(10:14:44) _Nesshof_: mdamboldt !
(10:14:56) _Nesshof_: :-)
(10:15:48) _Nesshof_: mdamboldt ?
(10:15:54) mdamboldt: ?
(10:15:55) stx12: he is kidding, or not, mdamboldt?
(10:16:01) rtimm: Is this similar to what you are looking for: http://wiki.services.openoffice.org/wiki/New_Translation_Process_%28Pootle_server%29
(10:17:25) _Nesshof_: rtimm: the question is more how the developer have to prepare his strings that they get into that process I think
(10:17:41) rtimm: Ah, OK. I understand.
(10:17:55) _Nesshof_: rtimm: has ivo some documentation around this topic ?
(10:19:09) rtimm: _Nesshof_: Sorry, I do not know :-(
(10:21:38) _Nesshof_: all waiting for mdamboldt to come back to life ?
(10:21:41) stx12: so, were are hoping that with the 3.0 codeline and extensions in the repository all things will be good...
(10:22:56) mdamboldt: _Nesshof_: Still don't get why I should pick this AI.
(10:23:20) _Nesshof_: mdamboldt: you're the PM for this ?
(10:23:36) mdamboldt: For translation?
(10:24:54) mdamboldt: I will talk to Juergen about this, he was working on all the translation related stuff in the past. Don't know where he is today.
(10:25:07) _Nesshof_: ok, give the AI to me, I will try to transfer it then to NF since I'm just a guest here
(10:25:17) stx12: thanks for clarifying the responsibility offilne
(10:26:02) stx12: i guess mdamboldt and _Nesshof_ will jointly visit NF
(10:27:10) stx12: who btw has the next AI together with JSC:
(10:27:11) stx12: 2008_04_24: Give an overview of how to do this decoupling of translation cycles
(10:27:42) stx12: i guess we have no update on that?
(10:28:09) stx12: the next one has a due date in octiober:
(10:28:13) stx12: 2008-07-31: Propose workflow for localization of dynamic extension specific content (e.g. descriptions)
(10:28:18) _Nesshof_: i think this is dependent from the previous item
(10:28:27) stx12: that's it for the AIs.
(10:28:36) stx12: Roundtable Items?
(10:28:43) mdamboldt: none from me
(10:28:44) bettina-h: Yes.
(10:28:52) bettina-h: We have currently english tags in the properties of the english templates. As we have the possibility to select the language on the templates web site, one assumes, that the tags will change according the selected language too (not only the templates describtion).
(10:28:54) bettina-h: First question: How will we handle to have available the tags in the appropriate language? Should the german, french, etc. templates have the translated tags already included, like the english ones of template pack 2? Or do we want to have english tags in all templates first and then the tags are translated peu a peu? Or any other solution?
(10:28:55) bettina-h: Second question / remark: If we have the tags on the template web site and template related stuff (description) appear in the language, the user has selected, the categories business, education and private and their subcutegories need to be available in the appropriate language too. And the search is then also language dependend. It would be great and quite helpful for the user to have...
(10:28:57) bettina-h: ...changed the named content according his language selection (currently english, german, french).
(10:29:55) b_osi_away [n=b_osi@] a rejoint le salon.
(10:30:39) bettina-h: What do you think?
(10:31:24) b_osi_away est désormais connu sous le nom de b_osi
(10:32:14) stx12: hm, i'm a bit overwhelmed...
(10:32:19) b_osi: sorry lost connection since 10:17...
(10:33:00) bettina-h: I need to say that I helped to add the english tags into the english templates of pack 2, which will be put on the web site, means they are not part of the documents commonly.
(10:34:55) stx12: IIUC the first question, then we should make the existence of tags not a prerequisite for publishing templates.
(10:35:33) mdamboldt: To be honest I don't know the template site at all...
(10:35:33) mdamboldt: So I'm not sure what the answers on your questions would be. For extensions the tags were entered when publishing the extension, so the approach for templates is different?
(10:36:02) bosi a quitté le salon (quit: Read error: 110 (Connection timed out))
(10:36:12) mdamboldt a quitté le salon (quit: Excess Flood)
(10:37:40) bettina-h: The idea is, to read out the tags out of the template properties...
(10:37:59) bettina-h: to make easy their availability.
(10:38:19) bettina-h: From the ux point of view...
(10:38:48) bettina-h: it would be great to have the content available according the selected language.
(10:39:07) bettina-h: The content of the web site (as described above).
(10:39:39) bettina-h: It would be helpful, if bosi could give us the status about it.
(10:40:12) bettina-h: He tried something out, but had some problem. So we can discuss it today.
(10:42:15) stx12: it seems we have to make ourselves familiar with the template site: templates.services.openoffice.org is up; Protected by: odie - garfield
(10:43:37) stx12: bettina-h, b_osi, could you go ahead and discuss bettina-h's question?
(10:43:58) b_osi: I would stay with, to put the tags in the language of the template into the template;
(10:45:04) b_osi: the template categories would have to be translated by enableing a new language
(10:45:14) Zero_Dogg a quitté le salon
(10:47:16) b_osi: It should be the target to only show content of the selected language of the user.
(10:47:34) stx12: that sounds good as a default
(10:47:46) bettina-h: So we will have available the tags, categories, template description, button text (instead of "Use it" translated)? Great!
(10:47:55) stx12: nevertheless it might be good to allow search vor templates in another language
(10:48:35) b_osi: I heve not tried the search jet, maybe it works this way ;-)
(10:48:50) mdamboldt [n=md97092@sd-socks-197.staroffice.de] a rejoint le salon.
(10:49:18) ***mdamboldt Fu%$! Pidgin irc client...
(10:49:39) b_osi: I'm currently checking the upload, will do the entry pages tomorrow, and take a look on language dependent stuff next week.
(10:50:43) bettina-h: Apropos search...
(10:50:49) mdamboldt: How can I access http://templates.services.openoffice.org/ ?
(10:51:02) stx12: it seems we have to make ourselves familiar with the template site: templates.services.openoffice.org is up; Protected by: odie - garfield
(10:57:19) stx12: so, is there anything you need as further input today?
(10:57:52) bettina-h: Do we need the fileds who is new and who is online?
(10:58:01) bettina-h: I don't see the sence.
(10:58:38) mdamboldt: I think the numbers are ok, but the user names should not show up from my point of view.
(10:59:14) bettina-h: So we take out who is new?
(10:59:14) b_osi: it is not intended to leave it there. they will vanish.
(10:59:26) bettina-h: ok, thank you.
(11:01:05) stx12: as said I think it would be good to have a look at the site and comment on the list...
(11:01:23) stx12: anything else for today?
(11:01:29) mdamboldt: no
(11:01:34) bettina-h: no
(11:01:48) b_osi: no
(11:02:00) stx12: have a nice day then...
(11:02:12) mdamboldt: by
(11:02:13) bettina-h: bye.
Personal tools