- From: Yves Savourel <ysavourel@translate.com>
- Date: Wed, 28 Feb 2007 09:08:04 -0700
- To: <public-i18n-its@w3.org>
Subject: ITS Teleconf - Wednesday Feb-28-2007 15:00 UTC ======================================================= Last minutes: http://www.w3.org/2007/02/21-i18nits-minutes.html Agenda: http://lists.w3.org/Archives/Member/member-i18n-its/2007JanMar/0127.html IRC Log: http://www.w3.org/2007/02/28-i18nits-irc Present: Andrzej, Jirka, Yves Regrets: Christian, Sebastian, Felix === Review of the action items: There was no action items === Discussions --- Best Practices Working Draft Yves described the structure of the BP document: Intro, BP for developers, BP for authors, then a section with common examples and general ITS usage, then the section of ITS used with existing examples. Jirka is working on ITS + DocBook. Andrzej: May need section on 'do not use entities references' Yves: in addition to BP 17? (which is more general) Andrzej: using entities has other issue (like encoding mix up, etc.) The group then went through the few BP articles listed in the agenda: - Best Practice 1: Provide xml:lang to specify language content: http://www.w3.org/International/its/techniques/its-techniques.html#DevLa ng All: looks fine. - Best Practice 11: Specify the language of the content: http://www.w3.org/International/its/techniques/its-techniques.html#AuthL ang Jirka/Yves: may need to underline the need for xml:lang (vs another attribute) AI: Yves to re-word a note for this. - Best Practice 3: Avoid translatable attributes: http://www.w3.org/International/its/techniques/its-techniques.html#DevAt tributes AI: Yves to add a note in BP 3 about nested elements and the fact that default is no-trans for attributes. - Best Practice 4: Indicate the translatability of elements and attributes: http://www.w3.org/International/its/techniques/its-techniques.html#DevTr ans Jirka: Example 6 may need more explanation. <del> is having effect on segmentation, may need to refere to element-within text as well. AI: Yves to add a note in BP 4 on example where del breaks segmentation - Best Practice 5: Provide a way to override translatability information: http://www.w3.org/International/its/techniques/its-techniques.html#DevTr ansOver Yves: do we need 'or an equivalent attribute'? Jirka: no, this is for new schema they should use its:translate. Yves; we can split the section in normal/legacy like for language info AI: Yves to add a note in BP 5 to remove 'or equivalent' AI: Yves to add a note in BP 5 to split in 2 normal usage and legacy (with 2 examples) - Best Practice 17: Ensure any inserted text is context-independent http://www.w3.org/International/its/techniques/its-techniques.html#AuthI nsText Andrzej: Missing 'u' in one of the Polish words. Jirka: adding Xinclude would be good. AI: Yves to add a note in BP 17 to add reference to Xinclude --- Next face-to-face meeting. Yves: Christian has made some progress in finding a location/sponsor. - Other business No other business. Meeting closed Action Items Summary: -01 NEW: Yves to add a note in BP 11 to underline the need for xml:lang -02 NEW: Yves to add a note in BP 3 for nested element and default is no-trans for attribute -03 NEW: Yves to add a note in BP 4 on example where del breaks segmentation -04 NEW: Yves to add a note in BP 5 to remove 'or equivalent' -05 NEW: Yves to add a note in BP 5 to split in 2 normal usage and legacy (with 2 examples) -06 NEW: Yves to add a note in BP 17 to add reference to Xinclude -end-
Received on Wednesday, 28 February 2007 16:08:12 UTC