| 00000 |
1.16 Inline codes should have a way to store information about the effect on the segmentation |
Yves Savourel
|
2011-09-01 20:47 |
| 00001 |
Re: [xliff-inline] 1.16 Inline codes should have a way to store informationabout the effect on the segmentation |
David Walters
|
2011-09-01 22:00 |
| 00002 |
RE: [xliff-inline] Sample for metadata inline representation |
Lieske, Christian
|
2011-09-06 12:28 |
| 00003 |
RE: [xliff-inline] Req 1.15 Representation of invalid XML characters |
Lieske, Christian
|
2011-09-06 12:42 |
| 00004 |
RE: [xliff-inline] Sample for metadata inline representation |
Lieske, Christian
|
2011-09-06 12:56 |
| 00005 |
RE: [xliff-inline] 1.16 Inline codes should have a way to storeinformation about the effect on the segmentation |
Lieske, Christian
|
2011-09-06 13:00 |
| 00006 |
Teleconference - Sep-13-2011 |
Yves Savourel
|
2011-09-12 14:51 |
| 00007 |
RE: [xliff-inline] 1.16 Inline codes should have a way to store information about the effect on the segmentation |
Yves Savourel
|
2011-09-12 15:39 |
| 00008 |
RE: [xliff-inline] Req 1.15 Representation of invalid XML characters |
Yves Savourel
|
2011-09-12 16:57 |
| 00009 |
RE: [xliff] RE: [xliff-inline] Req 1.15 Representation of invalid XML characters |
Yves Savourel
|
2011-09-13 02:48 |
| 00010 |
RE: [xliff-inline] Teleconference - Sep-13-2011 - Summary |
Yves Savourel
|
2011-09-13 15:18 |
| 00011 |
Representing information for the starting/ending/standalone parts |
Yves Savourel
|
2011-09-19 16:39 |
| 00012 |
RE: [xliff-inline] Representing information for the starting/ending/standalone parts |
Schnabel, Bryan S
|
2011-09-19 18:25 |
| 00013 |
RE: [xliff-inline] Representing information for the starting/ending/standalone parts |
Yves Savourel
|
2011-09-20 10:58 |
| 00014 |
Sub-flows example, etc. |
Yves Savourel
|
2011-09-23 17:04 |
| 00015 |
RE: [xliff-inline] Sub-flows example, etc. |
Yves Savourel
|
2011-09-23 17:07 |
