Created attachment 180733 [details] short values for textDirection There are these problems: The values 'lr' 'lrV' 'rl' 'rlV' 'tb' and 'tbV' of element <textDirection> in OOXML are not supported at all. But those are the only values in the ISO version of OOXML and the newer ECMA-376 versions. LibreOffice supports only the old long values like 'btLr'. Word writes the short values, when it saves the file as "Strict Open XML Document". Test file: "Made manu 2char.docx". Open the file in LO, all texts are in normal orientation. And the old values have problems too: [1] 'tbLrV' (mongoleanVert) is not supported. [2] 'tbRl' (vert) and 'tbRlV' (eaVert) are rendered the same. [3] The text belonging to 'tbRLV' is correctly rendered with not rotated east Asian characters (eaVert), but written to file as 'tbRL', which means rotated east Asian characters. So the saved text looks different in Word. [4] 'lrTbV' (rotated eaVert) is not supported. It us used in east Asian table layout for row and column headers, same as we in Latin context use horizontal and vertical text in table row and column headers. Test file: "Made manu 4char.docx"
Created attachment 180734 [details] screenshot for short values
Created attachment 180735 [details] long values for textDirection
Created attachment 180736 [details] screenshot for long values
Moving to NEW. @Regina, do you plan to work on it ? Otherwise, do you think this could be turned into an easyhack ?
No, I do not plan to work on it, because I will stay in areas with shapes, where I more familiar with. It should be possible to map the short form of the attribute values to the long form on import. That is likely an easyHack. Writing out the short form on export is currently not good. That should only be done, when reading is implemented in all active versions and in the last "end of life" version. Because LO does not write strict OOXML, where it would be necessary, a change in the export filter is not urgent. I consider fixing the errors in the long form of the attribute values not an easyHack. It does not only need changes in the import and export filters but likely in the rendering engine too.
I have ask on the dev-list, whether this might be an easyHack, read https://lists.freedesktop.org/archives/libreoffice/2022-July/089178.html It seems it is usable as easyHack for persons interested in parser.