Happy New Year all!
I was looking at the example under heading 4.7.2.2 of the
XLIFF 2.0 Specification and wondering if we’re missing a Text/Value/Content property for all inlines or whether the `disp` and `equiv` properties are sufficient?
"source":
[
{
"text":
"Text in "
},
{
"disp":
"\\b ",
"id":
"1",
"kind":
"sc"
},
{
"text":
"bold"
},
{
"disp":
"\\i ",
"id":
"2",
"kind":
"sc"
},
{
"text":
"and"
},
{
"disp":
"\\b0 ",
"kind":
"ec",
"startRef":
"1"
}
},
{
"text":
" italics "
},
{
"disp":
"\\i0",
"kind":
"ec",
"startRef":
"2"
}
}
]
In XML we have both `disp` and `equiv` attributes PLUS the content of the element. In JSON we have only the properties.
| |||||||||||
| |||||||||||
| Vistatec House, 700 South Circular Road, Kilmainham, Dublin 8, Ireland. | |||||||||||
| |||||||||||
| Email: phil.ritchie@vistatec.com | |||||||||||
| |||||||||||
| |||||||||||
|