https://bugs.documentfoundation.org/show_bug.cgi?id=165193
--- Comment #5 from Eyal Rozenberg <[email protected]> --- (In reply to Mike Kaganski from comment #4) > How is this LibreOffice bug? How it happened that this got filed to this bug > tracker? In a word: compatibility. But let me elaborate. First, please see the blocked meta-bug regarding how this is hurting users in a real-life scenario. Also remember, that we tell people these days to consider just using ODTs for collaboration with MSO-using people, as MSO supports it. Now, there are three possibilities regarding what's going on here: 1. LO's interpretation of this ODT is valid, MSO's is invalid. 2. LO's interpretation of this ODT is invalid, MSO's is valid. 3. Both interpretations are valid. In the first, and likely, case - we could (and I believe we should) see if we could take some kind of precautionary measure to reduce the chance of mis-interpretation. That could be: 1.1 Presenting a warning dialog when saving files with style names which are identical up to letter case. Perhaps a warning which the user could dismiss permanently. 1.2 Adding an MS-Office compatibility option, forbidding such cases and requiring the user to change style names to avoid them. 1.3 At a lower level - perhaps tweaking what we write to the ODF without changing the semantics for us, but getting MSO to recognize that there are two styles. e.g. maybe something about the style's name vs display name? I don't know. Maybe this is impossible. In the second case - we have an ODF compliance bug. In the third case, the ODF spec probably has a bug, and then I'm not sure what should be the proper course of action. -- You are receiving this mail because: You are the assignee for the bug.
