[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF Inline Markup Subcommittee Teleconference - Dec-13-2011
XLIFF Inline Markup Subcommittee Teleconference Every second Tuesday of every month at 15:00 UTC 7:00am PT, 8:00am MT, 10:00am ET, 11:00 Montevideo, 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 The summary of our main items is here: http://wiki.oasis-open.org/xliff/OneContentModel/Requirements Draft is under SVN, here: http://tools.oasis-open.org/version-control/svn/xliff/trunk/inline-markup/ (this will be replaced by DocBook version soon) === Type of codes Decision on what set of codes to use: a) ph/pc/sc/ec, or b) ph/sc/ec, or c) ph/pc, or d) ph. http://lists.oasis-open.org/archives/xliff-inline/201111/msg00004.html === Annotations representation (req 1.5: Must allow to associate spans of content with metadata) Current proposed representation: http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html <mrk [id='id'] type='type' [value='some value'] [ref='someId'] [translate='yes|no']>...</mrk> --- Overlapping mrk: -> split them and merge them as needed. May require an attribute to make the distinction between lone consecutive annotations and split annotations. --- annotation with only translate attribute. What type value to use? -> 'generic' Yves was to bring the question of schema version 1.1 vs 1.0 to the TC. -> Done here: http://lists.oasis-open.org/archives/xliff/201111/msg00044.html One answer: http://lists.oasis-open.org/archives/xliff/201111/msg00046.html === What about crc and assoc? Those are not needed was last meeting consensus. Yves had the action item to ask to TC if anyone is using crc or assoc and report on current status for those. -> Done here: http://lists.oasis-open.org/archives/xliff/201111/msg00051.html === Representation of editing hints Need to have notation for 'permissions' Current permission we thought about: 1: a code can be deleted 2: a code can be replicated 3: a code can be moved out of its original order 4 (possibly): a code can be moved outside its original parent span All were to think about representation for hints. See: http://lists.oasis-open.org/archives/xliff-inline/201111/msg00008.html === Bi-direction markers Several tools use Unicode characters in 1.2. Goes against W3C recommendation but seems common practice. -> need to know about other tools -> ask for info to W3C Done Some reference material: - http://www.w3.org/International/questions/qa-bidi-controls - http://www.w3.org/International/wiki/BidiProposal === Codes and effect on segmentation (req 1.16: Inline codes should have a way to store information about the effect on the segmentation) Related email: http://lists.oasis-open.org/archives/xliff-inline/201109/msg00005.html === Representation of added codes Need to clarify use of duplicated code. e.g. why not re-use same code? (See http://lists.oasis-open.org/archives/xliff-inline/201110/msg00021.html) === Any other business --- I assume Andrew-P is in Pacific time zone. That would make now 2 members for 7am. Do we need/is it possible/ to shift the time of the SC 1 hour later? -end
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]