public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Docx reader ; style picking algorithm
Date: Thu, 1 Jan 2015 08:05:33 -0800 (PST)	[thread overview]
Message-ID: <224dcd62-a503-40a9-bd4b-a7009abd559a@googlegroups.com> (raw)
In-Reply-To: <dc85a2ba-1117-4ff3-9b53-edb5b36a9f73-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]

Yep -- a few major styles (headers, block quotes) have been addressed in 
the reader to make sure they work in different languages.

As far as the question of user-defined paragraph styles go -- the main 
to-do now is parsing the style file for paragraph styles similarly to how 
we already do it for character styles. There are additional details and 
complications which make it a bit harder, but it's doable, and just waiting 
on developer time. Eventually, user-defined styles that inherit from some 
set of base semantic styles will work. (This is all in the reader.)

What will probably never work is being able to guess that your user defined 
style for headers which is just big and bold is really for headers. In 
other words, paragraph styles will have to inherit from something semantic, 
and not just be be a collection of visual character styles.

On Thursday, January 1, 2015 9:50:49 AM UTC-5, Ghlen Livid wrote:
>
> I think what you are referring to is related to 
> https://github.com/jgm/pandoc/issues/1607 and 
> https://github.com/jgm/pandoc/issues/1692, please see revelant 
> discussions. 
> Basically, docx is a mess. 

-- 
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/224dcd62-a503-40a9-bd4b-a7009abd559a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3194 bytes --]

      parent reply	other threads:[~2015-01-01 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 21:48 Kjetil Flovild-Midtlie
     [not found] ` <4b2f3216-fc6c-4552-8bf0-3cd263ebc143-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-31 11:20   ` Kjetil Flovild-Midtlie
     [not found]     ` <1bb6000f-1dc7-4a1f-9050-188f03b8d4d9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-31 15:55       ` Mark Szepieniec
2015-01-01 14:50   ` Ghlen Livid
     [not found]     ` <dc85a2ba-1117-4ff3-9b53-edb5b36a9f73-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-01 16:05       ` Jesse Rosenthal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=224dcd62-a503-40a9-bd4b-a7009abd559a@googlegroups.com \
    --to=jrosenthal-4gnrotwusre@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).