Re: Please give the Docx reader a test drive

[Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org>]

As has been mentioned, this thread was a call for testing way back
when. It's not really the best place to report this sort of thing.

But if you do have a bug -- especially if it's a new regression -- I'd
love to hear about it! Can you post an issue on the github issue
tracker?

--Jesse

russurquhart1 <russurquhart1-H+0wwilmMs3R7s880joybQ@public.gmane.org> writes:

> Hi,
>
> I have some issue with the latest Docx reader. Is there a way to get your 
> sandbox version for windows?
>
> Thanks,m
>
> Russ
>
> On Monday, August 11, 2014 at 4:52:32 PM UTC-5, Jesse Rosenthal wrote:
>>
>> Dear All, 
>>
>> The MS Word docx reader in the new pandoc is working pretty well these 
>> days. Before the next release, though, I'd love it if we could run as 
>> many real-world Word docs through it as possible, to catch any odd 
>> behavior. As many different academic/professional fields as possible 
>> would be ideal, since I know everyone uses word a bit 
>> differently. Everyone testing it so far has brought some oversight to my 
>> attention, so I'd love to get more eyes on it. 
>>
>> If you do try it out, and you find something that doesn't behave 
>> correctly, please open an issue on my pandoc fork 
>> (<https://github.com/jkr/pandoc.git>), and send me the document over 
>> email if it's possible to share it. If you can't share it, it would be 
>> great if you could try to reproduce the issue in a different document. 
>>
>> Some notes: 
>>
>>   - All text, and all text formatting (unless it comes from an unusual 
>>     style) should be preserved. If it isn't, it's a bug. 
>>
>>   - There's not much we can do, with a few exceptions, with ad-hoc 
>>     visual stylization: making columns by pressing space a lot, pressing 
>>     return to make the end-of-the-line a bit prettier. The rule of thumb 
>>     is: can the property in question stand a change in margins and font? 
>>     If so, we should probably be able to interpret it. If not, we 
>>     probably can't. 
>>
>>   - Headers, titles and the like will be interpreted correctly if they 
>>     have the correct style. The reader can't guess at a header just 
>>     because some text is in bold, or uses another font. (Though at some 
>>     point in the future, I might introduce a filter with some heuristics 
>>     for guessing.) 
>>
>>   - Block quotes should be picked up by either styling with Quote or 
>>     BlockQuote, or by block indentation. If someone uses another style 
>>     to produce a blockquote, please let me know, so I can add it to the 
>>     list. 
>>
>>   - Track-changes can be used with the 
>>     "--track-changes=accept|reject|all". accept will take the 
>>     insertions, reject will stick with the deletions, and all will put 
>>     in everything, marked up with spans. 
>>
>>   - Equations should appear as LaTeX. 
>>
>> Anyway, please do give it a try and let me know, through the channels 
>> above, what weirdnesses you encounter. 
>>
>> To get the development pandoc, it's probably best to use a cabal sandbox 
>> (available, I believe in cabal >= 1.18). 
>>
>>     git clone https://github.com/jgm/pandoc.git 
>>     cd pandoc 
>>     cabal update 
>>     cabal sandbox --init 
>>     cabal install --only-dependencies 
>>     cabal install 
>>
>> The binary will then be located in pandoc/.cabal-sandbox/bin. 
>>
>> Thanks, 
>> Jesse 
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/97f48a84-e4f7-4617-95be-69493a3b47fa%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.