[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF Inline Markup Subcommittee Teleconference - Oct-09-2012
XLIFF Inline Markup Subcommittee Teleconference Oct-09-2012 Every second Tuesday of every month at 14:00 UTC 7:00am PT, 8:00am MT, 10:00am ET 3:00pm London, 4:00pm Berlin Teleconference meeting place: https://www1.gotomeeting.com/join/408998929 Meeting ID: 408-998-929 You can use the following US phone number, or the VOIP option provided by GoToMeeting: Dial 630-869-1010 Access Code: 408-998-929 Latest draft is here: See http://tools.oasis-open.org/version-control/svn/xliff/trunk/xliff-20/xliff-core.pdf === type for inline codes Composite values for the type attribute Something like this: type ::= <category>['/'<subcategory>] <subcategory> ::= <authority>':'<value> ACTION ITEM: Jung will try to come up with an initial list of main types: Done -> See here: https://lists.oasis-open.org/archives/xliff-inline/201210/msg00000.html === fs attribute Bryan has been working of the fs attribute since a while: https://lists.oasis-open.org/archives/xliff-inline/201210/msg00006.html and: https://lists.oasis-open.org/archives/xliff-inline/201210/msg00008.html === Maximum length Status from Fredrik (if needed) === Annotations representation ACTION ITEM: Yves to work on implementation. -> on going === Elements and Attributes Names Time to start choosing final names for the inline markup. See spreadsheet here: https://docs.google.com/spreadsheet/pub?key=0Av8I1YVQlYmsdEwtZ0VEVmo5Y0ZLTndEcUlFMzZnZmc&output=html === Namespace? Using the namespace of the core seem to be the consensus Will close this item. === Any other business Next meeting Nov-13. (Not affected by difference in daylight time change date between US and Europe) -end
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]