ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context -> docx ??
Date: Wed, 14 Jan 2015 21:15:38 +0100	[thread overview]
Message-ID: <54B6CE6A.3080501@gmx.es> (raw)
In-Reply-To: <20150114185550.05f3add2@iram-ha-003587.extra.cea.fr>

On 01/14/2015 06:55 PM, Alan BRASLAU wrote:
> Using ConTeXt (not emacs, markdown, or other such things...) you can
> indeed export to xml, xhtml, and create epub files.
> [...]
> The xhtml file can be read in a browser.
> (some tools seem to have problem with the hyphen=yes option)

I don’t know whether it makes sense to add discretionary hyphens to
texts, ewhen a browser can hyphenate it
(http://css-tricks.com/almanac/properties/h/hyphenate/).

This would make also searching harder.

And my experience with ePub readers (Adobe Reader Mobile 9) is that they
are interpreted as zero-width spaces
(http://www.mobileread.com/forums/showthread.php?t=28139).

BTW, ARM 9 doesn’t handle zero-width spaces right either. It interprets
them as standard spaces.

> There must be some way to get this into Word...

pandoc may be the way.

I say “may be” instead of “is” because pandoc ignores some attributes
when converting from XHTML
(http://pandoc.org/try/?text=%3Cp%3EThis+is+sample+with+a+foreign+word%3A+%3Cem+lang%3D%22de%22%3EFremdsprache%3C%2Fem%3E.%3C%2Fp%3E&from=html&to=markdown).

Just in case it helps,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2015-01-14 20:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 19:59 Idris Samawi Hamid ادريس سماوي حامد
2015-01-13 21:34 ` Marcin Borkowski
2015-01-14 17:55   ` Alan BRASLAU
2015-01-14 18:58     ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 19:58       ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 20:03         ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 20:15     ` Pablo Rodriguez [this message]
2015-01-14 20:29       ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 21:25         ` Peter Münster
2015-01-14 21:38         ` Aditya Mahajan
2015-01-14 22:11           ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 21:59         ` Pablo Rodriguez
2015-01-14 22:22           ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-15  8:01             ` Alan BRASLAU
2015-01-15 14:43               ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-15 16:03                 ` Wolfgang Schuster
2015-01-14 20:50     ` Marcin Borkowski
2015-01-14 18:44   ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 19:58 ` Pablo Rodriguez
2015-01-17 14:45   ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-17 20:32     ` Pablo Rodriguez
2015-01-17 21:06       ` Idris Samawi Hamid ادريس   سماوي حامد
2015-01-20 17:46         ` Pablo Rodriguez

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=54B6CE6A.3080501@gmx.es \
    --to=oinos@gmx.es \
    --cc=ntg-context@ntg.nl \
    /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).