| 1 |
XLIFF Inline Markup Subcommittee Teleconference - Dec-13-2011 - Summary |
16 |
Dec 2011 |
| 2 |
Sample for metadata inline representation |
15 |
Aug 2011 |
| 3 |
Inline code SC Meeting - June-14 |
13 |
Jun 2011 |
| 4 |
Representing information for the starting/ending/standalone parts |
13 |
Sep 2011 |
| 5 |
Teleconference - Aug-10-2010 - 13:30 UTC |
9 |
Aug 2010 |
| 6 |
Teleconference - Sep-14-2010 - 13:30 UTC |
9 |
Sep 2010 |
| 7 |
Various XML constructs in inline content |
9 |
Jul 2011 |
| 8 |
Req 1.15 Representation of invalid XML characters |
9 |
Aug 2011 |
| 9 |
Splitting non-clonable codes |
9 |
Feb 2012 |
| 10 |
Type of codes |
8 |
Nov 2011 |
| 11 |
1.14. Should be able to represent the mutual relationships between a nested flow of text and its parent |
7 |
Aug 2011 |
| 12 |
Editing operations and spliting segment |
7 |
May 2012 |
| 13 |
XLIFF Inline Markup Subcommittee Teleconference - Sep-11-2012 - Summary |
7 |
Sep 2012 |
| 14 |
Requirements - #9 |
6 |
Aug 2010 |
| 15 |
Reference to opening code |
6 |
Jul 2011 |
| 16 |
Native data - "outside" representation |
6 |
Jul 2011 |
| 17 |
SC face to face meeting? |
6 |
Feb 2012 |
| 18 |
Proposed requirement for inline SC: XML well-formed-ness as adesign goal for XLIFF 2.0 inline markup |
5 |
May 2010 |
| 19 |
Inline codes properties |
5 |
Apr 2011 |
| 20 |
Inline spans |
5 |
May 2011 |
| 21 |
v1.2 to v2.0 mapping |
5 |
Oct 2011 |
| 22 |
Type of inline codes - ballot |
5 |
Dec 2011 |
| 23 |
[xliff-inline] Semantics for canReorder editing hint |
5 |
Feb 2012 |
| 24 |
mrk and id |
5 |
May 2012 |
| 25 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Nov-13-2012 - Summary |
5 |
Nov 2012 |
| 26 |
Personal Action Item to Review the existing Requirements |
4 |
Oct 2010 |
| 27 |
Storing native data |
4 |
Dec 2010 |
| 28 |
1.3. Must be able to represent paired codes that have been separated |
4 |
Aug 2011 |
| 29 |
[xliff-inline] Id attribute between source and target |
4 |
Oct 2011 |
| 30 |
mrk and translate |
4 |
May 2012 |
| 31 |
Feedback needed for Directionality |
4 |
Jul 2012 |
| 32 |
Definition of "inline code" |
3 |
Jul 2010 |
| 33 |
Requirements - #8 |
3 |
Jul 2010 |
| 34 |
1.15. Should be able to represent illegal XML characters in the content |
3 |
Aug 2011 |
| 35 |
1.5. Must allow to associate spans of content with metadata |
3 |
Oct 2011 |
| 36 |
[xliff-inline] Isolated paired codes |
3 |
Oct 2011 |
| 37 |
Inline Markup Teleconference |
3 |
Nov 2011 |
| 38 |
Attribute uniqueness |
3 |
Dec 2011 |
| 39 |
[xliff-inline] BiDi draft for discussion |
3 |
Apr 2012 |
| 40 |
Name changing and moving the proposal to the TC |
3 |
Dec 2012 |
| 41 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Dec-11-2012 - Summary |
3 |
Dec 2012 |
| 42 |
Inline Markup SC passes on its proposal to the TC |
3 |
Dec 2012 |
| 43 |
XLIFF Inline Markup Subcommittee Teleconference |
2 |
May 2010 |
| 44 |
Wiki cleanup + A concrete Scope Section |
2 |
May 2010 |
| 45 |
Teleconference - Jun-08-2010 - 13:30 UTC |
2 |
Jun 2010 |
| 46 |
Teleconference - Jul-13-2010 - 13:30 UTC |
2 |
Jul 2010 |
| 47 |
Teleconference - Oct-12-2010 - 13:30 UTC |
2 |
Oct 2010 |
| 48 |
Inline Markup - phase 2 |
2 |
Nov 2010 |
| 49 |
Teleconference - Nov-9-2010 - 14:30 UTC |
2 |
Nov 2010 |
| 50 |
XML 1.1 |
2 |
Jan 2011 |
| 51 |
Teleconference - Mar-08-2011 |
2 |
Mar 2011 |
| 52 |
XLIFF inline markup - Teleconference - Aug-09-2011 |
2 |
Aug 2011 |
| 53 |
1.16 Inline codes should have a way to store information about the effect on the segmentation |
2 |
Sep 2011 |
| 54 |
Sub-flows example, etc. |
2 |
Sep 2011 |
| 55 |
Code (and content) comparison |
2 |
Oct 2011 |
| 56 |
Permissons attributes |
2 |
Feb 2012 |
| 57 |
The Dublin Option |
2 |
Feb 2012 |
| 58 |
Dublin Face-to-Face |
2 |
Apr 2012 |
| 59 |
Face-to-Face Meeting of the inline markup SC in Dublin in June |
2 |
Apr 2012 |
| 60 |
Processing expectations for segment editing |
2 |
Apr 2012 |
| 61 |
Face to face |
2 |
Jun 2012 |
| 62 |
SC F2F outcome: Storing original data (IMPORTANT) |
2 |
Jun 2012 |
| 63 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - July-10-2012 - Summary |
2 |
Jul 2012 |
| 64 |
Names |
2 |
Sep 2012 |
| 65 |
annotation type |
2 |
Sep 2012 |
| 66 |
fs attribute on inline elements |
2 |
Oct 2012 |
| 67 |
Propose 2 enhancements to @fs |
2 |
Oct 2012 |
| 68 |
Test |
1 |
May 2010 |
| 69 |
Status of Inline markup for XLIFF 2.0 |
1 |
May 2010 |
| 70 |
Teleconference - May-10-2010 - 13:30 UTC |
1 |
May 2010 |
| 71 |
Teleconference - May-10-2010 - 13:30 UTC - Minutes |
1 |
May 2010 |
| 72 |
Requirements for inline markup |
1 |
May 2010 |
| 73 |
Requirement on marking spans of content |
1 |
Jun 2010 |
| 74 |
use case for xliff-inline markup |
1 |
Aug 2010 |
| 75 |
Requirement #13 |
1 |
Aug 2010 |
| 76 |
[xliff-inline] Teleconference - Nov-9-2010 ACTION ITEM "Iinitialdefinition for "what we code in the XLIFF content" |
1 |
Dec 2010 |
| 77 |
Teleconference - Nov-14-2010 - 14:30 UTC |
1 |
Dec 2010 |
| 78 |
Teleconference - Nov-14-2010 - Summary |
1 |
Dec 2010 |
| 79 |
Storing native data in inline codes |
1 |
Jan 2011 |
| 80 |
Teleconference - Jan-11-2011 - 14:30 UTC |
1 |
Jan 2011 |
| 81 |
Teleconference - Jan-11-2011 - Summary |
1 |
Jan 2011 |
| 82 |
Time for a new Time? |
1 |
Jan 2011 |
| 83 |
Representing natiave data of the inline codes |
1 |
Feb 2011 |
| 84 |
Teleconference - Feb-08-2011 - 15:00 UTC |
1 |
Feb 2011 |
| 85 |
Teleconference - Feb-08-2011 - 15:00 UTC - Summary |
1 |
Feb 2011 |
| 86 |
RE: Generic Inline Markup - Input Highly Appreciated (draft) |
1 |
Mar 2011 |
| 87 |
Teleconference - Apr-12-2011 |
1 |
Apr 2011 |
| 88 |
Teleconference - Apr-12-2011 - Summary |
1 |
Apr 2011 |
| 89 |
Teleconference - May-10-2011 |
1 |
May 2011 |
| 90 |
Unusual inline code examples |
1 |
May 2011 |
| 91 |
Teleconference - May-10-2011 - Summary |
1 |
May 2011 |
| 92 |
Summary |
1 |
May 2011 |
| 93 |
FW: [xliff] RE: [xliff-inline] Complex tag content |
1 |
Jun 2011 |
| 94 |
MY ACTION ITEM: Read Up on ID Approaches |
1 |
Jun 2011 |
| 95 |
Inline markup |
1 |
Jul 2011 |
| 96 |
Escaping non-Unicode Characters |
1 |
Jul 2011 |
| 97 |
1.12.3. to store a pointer to it along with its XLIFF representation |
1 |
Aug 2011 |
| 98 |
1.8. Must be able to identify uniquely an inline code within a segment |
1 |
Aug 2011 |
| 99 |
1.13. Must be able to represent separately different flows of text and codes when, in the original format, they are mixed together |
1 |
Aug 2011 |
| 100 |
ID values |
1 |
Aug 2011 |
| 101 |
Temporary Working Draft |
1 |
Aug 2011 |
| 102 |
Re: [xliff-inline] 1.16 Inline codes should have a way to store informationabout the effect on the segmentation |
1 |
Sep 2011 |
| 103 |
RE: [xliff-inline] 1.16 Inline codes should have a way to storeinformation about the effect on the segmentation |
1 |
Sep 2011 |
| 104 |
Teleconference - Sep-13-2011 |
1 |
Sep 2011 |
| 105 |
RE: [xliff-inline] Teleconference - Sep-13-2011 - Summary |
1 |
Sep 2011 |
| 106 |
Teleconference - Tuesday Oct-11-2011 |
1 |
Oct 2011 |
| 107 |
RE: [xliff-inline] Teleconference - Tuesday Oct-11-2011 - Summary |
1 |
Oct 2011 |
| 108 |
RE: [xliff-inline] Inline Markup Teleconference - Summary |
1 |
Nov 2011 |
| 109 |
Off topic:: Unclobberable Portions |
1 |
Nov 2011 |
| 110 |
The mrk element |
1 |
Nov 2011 |
| 111 |
Hint representation |
1 |
Nov 2011 |
| 112 |
Types of codes |
1 |
Dec 2011 |
| 113 |
XLIFF Inline Markup Subcommittee Teleconference - Dec-13-2011 |
1 |
Dec 2011 |
| 114 |
XLIFF Inline Markup Subcommittee Teleconference - Jan-10-2012 |
1 |
Jan 2012 |
| 115 |
XLIFF Inline Markup Subcommittee Teleconference - Jan-10-2012 - Summary |
1 |
Jan 2012 |
| 116 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Summary |
1 |
Feb 2012 |
| 117 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Summary (amended) |
1 |
Feb 2012 |
| 118 |
Adding inline codes |
1 |
Feb 2012 |
| 119 |
Inline markup SC teleconference - March-13-2012 |
1 |
Mar 2012 |
| 120 |
[xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Mar-13-2012 - Summary |
1 |
Mar 2012 |
| 121 |
Inline makrup Teleconference - Apr-10-2012 |
1 |
Apr 2012 |
| 122 |
RE: [xliff-inline] Inline makrup Teleconference - Apr-10-2012 - Summary |
1 |
Apr 2012 |
| 123 |
Validation question |
1 |
Apr 2012 |
| 124 |
Inline Markup Teleconference - May-08-2012 |
1 |
May 2012 |
| 125 |
RE: [xliff-inline] Inline Markup Teleconference - May-08-2012 - Summary |
1 |
May 2012 |
| 126 |
mrk and overlapping cases |
1 |
May 2012 |
| 127 |
Dublin face-to-face meeting |
1 |
Jun 2012 |
| 128 |
Record of AIs, To Dos, and new consensi from Inline F-2-F SC meeting 2012-6-14 |
1 |
Jun 2012 |
| 129 |
SC F2F outcomes |
1 |
Jun 2012 |
| 130 |
SC F2F: Recording location |
1 |
Jun 2012 |
| 131 |
Image of mrk proposal (for archive) |
1 |
Jun 2012 |
| 132 |
SC F2F outcome: Attribute for XML behavior |
1 |
Jun 2012 |
| 133 |
SC F2F outcome: Type attribute |
1 |
Jun 2012 |
| 134 |
SC F2F: Actions for day 2. |
1 |
Jun 2012 |
| 135 |
ITS in |
1 |
Jul 2012 |
| 136 |
SC F2F outcome: handling split |
1 |
Jul 2012 |
| 137 |
XLIFF Inline Markup Subcommittee Teleconference - July-10-2012 |
1 |
Jul 2012 |
| 138 |
Teleconference next week |
1 |
Aug 2012 |
| 139 |
XLIFF Inline Markup Subcommittee Teleconference - Sep-11-2012 |
1 |
Sep 2012 |
| 140 |
XLIFF Inline Markup Subcommittee Teleconference - Oct-09-2012 |
1 |
Oct 2012 |
| 141 |
RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Oct-09-2012 - Summary |
1 |
Oct 2012 |
| 142 |
attibute and element names |
1 |
Oct 2012 |
| 143 |
Type attributes in inline codes |
1 |
Oct 2012 |
| 144 |
Preparation for next week's call |
1 |
Nov 2012 |
| 145 |
XLIFF Inline Markup Subcommittee Teleconference - Nov-13-2012 |
1 |
Nov 2012 |
| 146 |
XLIFF Inline Markup Subcommittee Teleconference - Dec-11-2012 |
1 |
Dec 2012 |
| 147 |
This TC Workspace and email list is migrating |
1 |
Feb 2024 |
