XLIFF Inline Markup SC Public Documents
| XLIFF Inline Markup SC (Showing 5 of 5) | ||||||
| Document Name | # | Size | State | Submitter | Date | Action |
|---|---|---|---|---|---|---|
0 |
14K |
Draft |
Yves Savourel |
2012-12-18 |
||
Do you agree that the current SC proposal for the Inline Markup (with the small change in section 2.6.7.1 as described here: https://lists.oasis-open.org/archives/xliff-inline/201212/msg00004.html) should be send to the TC? | ||||||
0 |
12K |
Draft |
Yves Savourel |
2012-04-09 |
||
Should the Inline markup SC have a face-to-face meeting in Dublin on June 14th all day and June 15th morning. With a possible option for Friday afternoon as well. That option to be decided no later than during our teleconference call early next week, so people can make travel arrangements. | ||||||
0 |
19K |
Draft |
Yves Savourel |
2012-03-30 |
||
The face to face meeting would be in Dublin (extact location still TDB) on June-13 and June-14. | ||||||
0 |
19K |
Draft |
Yves Savourel |
2012-03-30 |
||
We can still have a 1.5 or 2 day meeting by using the Friday Jun-15 instead of the Wednesday Jun-13. This poll is to see how many of us could possibly make it also on the Friday. I've divided the question on morning / afternoon. | ||||||
0 |
14K |
Draft |
Yves Savourel |
2012-01-09 |
||
How should inline codes should be represented? Essentially this is to decide if span-like codes can be represented with span-like elements in XLIFF 2.0. In addition this also decides if sc/ec should be a special case of ph. a) ph, pc, sc, ec: ph for placeholder codes (e.g ) pc for well-formed span-like codes (e.g ...) sc/ec for span-like codes that are not well-formed. b) ph, sc, ec: ph for placeholder codes (e.g ) sc/ec represent all span-like codes (well-formed and not well-formed), no pc c) ph, pc: ph for placeholder codes (e.g ) and for not-well-formed span-like codes (no sc/ec) pc for well-formed span-like codes (e.g ...) d) ph: everything is represented with ph | ||||||
