The example file with AlternateContent wrappers for table element styles is handled correctly now by r1799733 and added as a unit test. Existing tests still pass for me, plus my own downstream integrations.
On Fri, Jun 23, 2017 at 1:07 PM Greg Woolsey <greg.wool...@gmail.com> wrote: > I checked in the units merge this morning. I'll dig more into what > drawing does for alternate content. > > On Fri, Jun 23, 2017, 12:57 Andreas Beeker <kiwiwi...@apache.org> wrote: > >> AlternateContent is also used in XSLF and XmlBeans provides either a >> XPath or a Cursor API, >> to access those - just have a look at XSLFDrawing - if you need help, I >> can support. >> >> So I'm waiting for your modifications (+EMUUtils merge), before preparing >> the release candidate. >> >> Andi >> >> On 6/23/17 8:44 PM, Greg Woolsey wrote: >> > In this particular case, the test file defines "mc:AlternateContent" for >> > some table styles. I've not played around with those, and the few >> cases I >> > see already in POI seem pretty specific to those areas of content. >> > >> > Anyone have strong opinions on whether XSSFTableStyle should do anything >> > with these? If so, anyone have experience with XMLBeans in the context >> of >> > finding and parsing sub-elements into CT* beans? >> > >> > My initial reaction is that this is a lightly used area and specific to >> 3rd >> > party implementations of OOXML with custom extensions, so doing nothing >> > beyond gracefully ignoring these is a viable option for now. >> > >> > On Fri, Jun 23, 2017 at 10:02 AM Greg Woolsey <greg.wool...@gmail.com> >> > wrote: >> > >> >> I'll take a look at that exception, I touched XSSFTableStyle. >> >> >>
