[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Amin Bandali]

Nicolas Floquet  writes:

> Le jeudi 16 mai 2019 à 17:16 +0200, Nicolas Floquet a écrit :
>> The problem is not solved on emacs 26.2.
>
> I have just humbly made a little commit wich is not the best solution,
> take in consideration that I am not a programmer… I can not currently
> do better ! :-)
> https://code.orgmode.org/nflqt/org-mode/commit/11206b40781b9f04912cb1c538a6b936c8dadc21
>

I set that mirror up last year around when the bug report was submitted.
I see in 50aca8422b [0] on the org-mode repo @ngz removed references to
the GitHub repo from lisp/ox-html.el, as I believe there was some talk
to use Emacs’s htmlfontify instead of htmlize.  But I’m not aware of any
progress on that front.  Further, references to the GitHub repo still
remain in lisp/ox-org.el, lisp/org-agenda.el, and lisp/org-manual.org;
the first two of which were addressed by @nflqt’s commit above.

[0]: 
https://code.orgmode.org/bzg/org-mode/commit/50aca8422b0afd4a2173ac93225fa9b39a94d8dd

@ngz, until such time as htmlfontify fully replaces org-mode’s uses of
htmlize, what do you think about (partially) reverting your 50aca8422b
and instead of linking to the htmlize repo on GitHub or no link at all,
link to https://code.orgmode.org/mirrors/emacs-htmlize instead?

>
>
>> Thank you for all the work done.
>
> Again.

Best,
amin

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I asked 

  > > Is the WebDAV server code free software?  Can you talk to such a
  > > server without any nonfree client software?

Fortunately, Nicolas Goaziou 's information
shows that using WebDAV is no problem.

  > There are 2 other ways to use Android MobileOrg not included in the
  > worg page:
  > 1. SSH
  > 2. Local filesystem

It sounds like modifying Android MobileOrg so it used only those
methods plus WebDAV, and not Dropbox, could result in a free program
that could be in f-droid.  It would be useful for someone to do that
and publish it under a different name.

Once that gets done, it would be good to make Emacs encourage people to
use _that version_ of Android MobileOrg.

Until then, Emacs (including Org-mode) should not say or do anything
that would be likely to lead users to use the existing MobileOrg.
We should remove that text soon, and put in new text about the new
version when that new version is available.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Michael Albinus]

Nicolas Goaziou  writes:

> Hello,

Hi,

>> Is the WebDAV server code free software?
>
> At least some implementations are, e.g., Nextcloud, listed in the FSF
> directory.
>
>> Can you talk to such a server without any nonfree client software?
>
> I do it with Gnome file manager. There is also an official client for
> Nextcloud, which is free.

For the records, Emacs 27.0.50 / Tramp 2.4.1-pre got a nextcloud client
for GNU/Linux systems. Like the Gnome File Manager it uses the GVFS
library and tools.

> Regards,

Best regards, Michael.

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Bingo UV]

Hi RMS, Nicolas
   The concrete software MobileOrg on Android is somewhat of an orphan.
   It may not revive as itself. But there is also a protocol mobileorg,
   which the manual alludes to, though does not document directly. That
   protocol is very much an enabler of software freedom, and it is
   important for the next MobileOrg to be written. I hope it survives
   these questions.

The protocol can be used to sync 2 sets of org-mode files between 2
emacs instances - without needing the iOS or Android versions of
MobileOrg. When fancypants sync systems like dropbox, git, syncthing,
rsync etc. are not available, the mobileorg protocol can be used to
transfer changes from one place to another.

As for the questions :

On Wed, 19 Sep 2018 21:50:26 -0400
Richard Stallman  wrote:
> 
> What is the source license of Mobile.org?

GPLv3
(https://github.com/matburt/mobileorg-android/blob/master/LICENSE.txt)

> 
Is it listed in f-droid.org?

It used to be, it has been kicked out of f-droid due to violating
policies : including dubious jars. Dropbox API that it was using was
surely non-free.


>   > [fn:146] An alternative is to use a WebDAV server.  MobileOrg
>   > documentation has details of WebDAV server configuration.
>   > Additional help is at this
>   > [[https://orgmode.org/worg/org-faq.html#mobileorg_webdav][FAQ
>   > entry]].  
> 
> Is this a way to use MobileOrg without Dropbox?
> 
> Is the WebDAV server code free software?  Can you talk to such a
> server without any nonfree client software?

There are 2 other ways to use Android MobileOrg not included in the
worg page:
1. SSH
2. Local filesystem


Also, since one can write one's own WebDAV server using specs, it
doesn't matter if some particular WebDAV servers are free or not.

thanks

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nicolas Goaziou]

Hello,

Richard Stallman  writes:

> What is the source license of Mobile.org?

It is GPL2+.

> Does Mobile.org for Android link with any nonfree libraries,
> such as Google Play Library?

No idea.

> Is it listed in f-droid.org?

Yes, it is.

> If there is a way to use Dropbox (for those operations that are
> necessary in this context) without running any nonfree client
> software, it would be ok to recommend using Dropbox _in that way_.
> (The operations necessary in this context must include creating an
> account.)

I don't know.

> Is this a way to use MobileOrg without Dropbox?

Yes, it is. MobileOrg just needs to get read/write access to some Org
files from anywhere. Dropbox is one way to do that. Any online storage
with WebDAV support fits the bill, too.

I think Dropbox is being mentioned because it may not be trivial for
users to do self-hosting or to find an ethical location for their files.
So, here comes the ready-to-use solution.

> Is the WebDAV server code free software?

At least some implementations are, e.g., Nextcloud, listed in the FSF
directory.

> Can you talk to such a server without any nonfree client software?

I do it with Gnome file manager. There is also an official client for
Nextcloud, which is free.

Regards,

-- 
Nicolas Goaziou0x80A93738

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

The crucial question here is whether Mobile.org is free software.  If
it is not, then GNU packages including their documentation should not
mention it at all.  See the chapter References in the GNU Coding
Standards.

What is the source license of Mobile.org?

Does Mobile.org for Android link with any nonfree libraries,
such as Google Play Library?  Is it listed in f-droid.org?

I don't think it is possible to have free apps for the iMonsters.
This is because iOS does not allow users to install modified versions
of apps, even if the app's source is released under a free license.


Another issue is the suggestion to use DropBox.
Normal use of Dropbox involves running nonfree JS software
(see https://gnu.org/philosophy/javascript-trap.html),
so we cannot recommend using Dropbox in the normal way.

If there is a way to use Dropbox (for those operations that are
necessary in this context) without running any nonfree client
software, it would be ok to recommend using Dropbox _in that way_.
(The operations necessary in this context must include creating an
account.)

However, the text you showed me does not include such a specific
recommendation, so we have to eliminate it.  We could reinsert the
discussion of Dropbox if and when someone writes text to recommend a
suitable specific way to use it.

  > [fn:146] An alternative is to use a WebDAV server.  MobileOrg
  > documentation has details of WebDAV server configuration.  Additional
  > help is at this 
[[https://orgmode.org/worg/org-faq.html#mobileorg_webdav][FAQ entry]].

Is this a way to use MobileOrg without Dropbox?

Is the WebDAV server code free software?  Can you talk to such a
server without any nonfree client software?


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nicolas Goaziou]

Hello,

Richard Stallman  writes:

> That may or may not be a problem, depending on what it says.  Can you
> show me what it actually says about those nonfree systems?

All references are related to the appendix about MobileOrg, an
application for viewing and capturing entries from a mobile device.
Relevant parts include references to Apple and Google products in
addition to Dropbox:

--8<---cut here---start->8---
MobileOrg is a companion mobile app that runs on iOS and Android
devices.  MobileOrg enables offline-views and capture support for an
Org mode system that is rooted on a "real" computer.  MobileOrg can
record changes to existing entries.

The [[https://github.com/MobileOrg/][iOS implementation]] for the /iPhone/iPod 
Touch/iPad/ series of
devices, was started by Richard Moreland and is now in the hands of
Sean Escriva.  Android users should check out 
[[http://wiki.github.com/matburt/mobileorg-android/][MobileOrg Android]] by
Matt Jones.  Though the two implementations are not identical, they
offer similar features.
--8<---cut here---end--->8---


--8<---cut here---start->8---
MobileOrg needs access to a file directory on a server to interact
with Emacs.  With a public server, consider encrypting the files.
MobileOrg version 1.5 supports encryption for the iPhone.  Org also
requires =openssl= installed on the local computer.  To turn on
encryption, set the same password in MobileOrg and in Emacs.  Set the
password in the variable ~org-mobile-use-encryption~[fn:145].  Note
that even after MobileOrg encrypts the file contents, the file name
remains visible on the file systems of the local computer, the server,
and the mobile device.
--8<---cut here---end--->8---


--8<---cut here---start->8---
For a server to host files, consider options like 
[[http://dropbox.com][Dropbox.com]]
account[fn:146].  On first connection, MobileOrg creates a directory
=MobileOrg= on Dropbox.  Pass its location to Emacs through an
initialisation file variable as follows:

#+begin_src emacs-lisp
(setq org-mobile-directory "~/Dropbox/MobileOrg")
#+end_src
--8<---cut here---end--->8---

Here is the footnote from the last excerpt:

--8<---cut here---start->8---
[fn:146] An alternative is to use a WebDAV server.  MobileOrg
documentation has details of WebDAV server configuration.  Additional
help is at this [[https://orgmode.org/worg/org-faq.html#mobileorg_webdav][FAQ 
entry]].
--8<---cut here---end--->8---

I think that is about it.

Regards,

-- 
Nicolas Goaziou0x80A93738

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > Note that the Org manual still talks about iOS and Android, which are
  > > not free either.

That may or may not be a problem, depending on what it says.  Can you
show me what it actually says about those nonfree systems?
-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Amin Bandali]

Nicolas Goaziou  writes:

> I removed htmlize URL from the error message. I also demoted the latter
> to a plain message. So, if htmlize is not installed, source blocks are
> not fontified.

I was going to suggest a less harsher and potentially more
helpful approach: in the short term, mirror the htmlize repo on
code.orgmode.org, the official Gogs instance where Org mode is
hosted and developed.  In the long term, work on replacing
htmlize with htmlfontify.

I set up a mirror: https://code.orgmode.org/aminb/emacs-htmlize

Assuming code.orgmode.org uses Gogs' default mirror settings, the
repo should be automatically synchronized with upstream roughly
every 8 hours or so.

This way, we'd still be able to point the users to a concrete
address to get htmlize from, without directly pointing them to a
proprietary platform.  Further, we're not claiminig copyright or
maintainership of the repo and we're merely mirroring it on a
freedom-respecting platform along with Org itself.

  -amin

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Kaushal Modi]

On Tue, Sep 18, 2018 at 10:22 AM Nick Dokos  wrote:
> Why is that a problem? What do we gain by doing that? What do we lose by 
> staying put
> on htmlize?
>
> These are not rhetorical questions: I really don't understand the problem.
>
> --
> Nick

I also don't get the problem. The software is free. If people don't
like the non-free JS on GitHub, they can get htmlize.el using a simple
wget or curl from
https://raw.githubusercontent.com/hniksic/emacs-htmlize/master/htmlize.el.

In any case, I have asked the htmlize.el author if he is willing to
assing his copyright to FSF in this GitHub Issue[0] for anyone
interested.

[0]: https://github.com/hniksic/emacs-htmlize/issues/23

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nicolas Floquet]

Le mardi 18 septembre 2018 à 11:37 +0200, Nicolas Goaziou a écrit :
> I read the thread multiple times already but I do not understand
> exactly the issue risen.

Actually, it's an ethical issue. That are not always easily solved with
technical solutions, I guess…

> From the OP: "Emacs quotes Github, a non-free platform." If that's
> the real problem, we can remove the location of the "htmlize" library
> from the error message and be done with it.

Indeed.

> Note that the Org manual still talks about iOS and Android, which are
> not free either.

It's true. I don't know what to think about this.


-- 
| Numérion  |  Nicolas Floquet |
+--+
| Services informatiques en logiciels libres   |
| XMPP : nf...@jabber.fr | Tél : 06.32.93.03.51|
| Ğ1 : BjZFP7UpKjJ9hbavhT2Ep2hP58noXp6xdPY4awsX17yD|
| PGP : 94C7 641B 719E B06A F406  7AB3 3709 C700 E548 F996 | 
+--+


signature.asc
Description: This is a digitally signed message part

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nick Dokos]

Eli Zaretskii  writes:

>> This is a genuine question: what /exactly/ do you want Org developers to
>> solve, assuming they can? Also, if they cannot, who is willing to give
>> them a hand?
>
> From my POV, the immediate problem is to switch Org-publish from using
> htmlize to htmlfontify.  Can this be done, please?
>

Why is that a problem? What do we gain by doing that? What do we lose by 
staying put
on htmlize?

These are not rhetorical questions: I really don't understand the problem.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Bernt Hansen]

Nick Dokos  writes:

> Adam Porter  writes:
>
>> I'm not an expert on this package nor this situation, however, looking
>> at the htmlize.el file shows:
>>
>> ;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018
>>
>> So it would appear that the package has existed longer than either
>> GitHub or Org.  I'm guessing that its author moved its primary repo to
>> GitHub after Org started using it.
>>
>> In hindsight, perhaps it would have been better to move htmlize into
>> Emacs before adding it to Org proper.  But many things are clearer in
>> hindsight.
>>
>> Regardless of where it is hosted, htmlize.el is Free Software, and it's
>> an optional addon to Org.  We can encourage its author to add it to
>> Emacs proper, or to ELPA.  But surely it's not necessary to censor the
>> mention of "GitHub" in the manual; it's simply a fact that GitHub exists
>> and that htmlize.el is currently hosted there.  It would seem
>> unreasonable for the Org maintainers to have reacted to htmlize.el's
>> moving to GitHub by removing htmlize.el support while it remains Free
>> Software, yet that's the logical conclusion of this argument.
>>
>
> I had exactly the same reaction.

Me too!

>
>> So please do not remove support for this package because of where its
>> repo happens to be hosted at the moment.  That would be a major
>> regression, and it would not be in users' best interests.  It would not
>> be fair to remove a major feature used by thousands of users and demand
>> that "someone" (since there is no one ultimately responsible) rewrite
>> large parts of ox-html.el to fix it.  It would at least seem fair for
>> those insisting on the change to do the necessary work.
>>
>
> I don't usually +1 replies but I wanted to chime in my agreement with
> Adam here.  Thanks for taking the time to put your (and my!) thoughts
> into words.
>
> If Github is indeed the sticking point, why can't it (the htmlize
> repo) be cloned on the same server as org-mode (possibly as its own
> repo, possibly as a git submodule)? It's not a fast moving target: a
> handful or two of commits per year. The doc can then avoid the Gihub
> ref (although it does seem silly to pretend that Github does not
> exist).

I completely agree with Adam and Nick's take on this issue.  Breaking
HTML export by removing htmlize is going to have a huge negative impact
on Org users and since the package is already free software what is the
point?

Regards,
Bernt

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Eli Zaretskii]

> From: Nicolas Goaziou 
> Cc: r...@gnu.org,  kaushal.m...@gmail.com,  n...@flqt.fr,  
> 32...@debbugs.gnu.org
> Date: Tue, 18 Sep 2018 11:37:15 +0200
> 
> This is a genuine question: what /exactly/ do you want Org developers to
> solve, assuming they can? Also, if they cannot, who is willing to give
> them a hand?

>From my POV, the immediate problem is to switch Org-publish from using
htmlize to htmlfontify.  Can this be done, please?

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nicolas Goaziou]

Hello,

Eli Zaretskii  writes:

> This is an Org issue, so I would like to hear from Org developers
> before I make up my mind.

I read the thread multiple times already but I do not understand exactly
the issue risen.

>From the OP: "Emacs quotes Github, a non-free platform." If that's the
real problem, we can remove the location of the "htmlize" library from
the error message and be done with it. Note that the Org manual still
talks about iOS and Android, which are not free either.

>From Richard Stallman: "Emacs should not advise people to load anything
from outside Emacs". Org Export already advises people to load LaTeX
libraries, MathJax, optionally minted, etc. Org Babel requires external
libraries like "asy-mode.el" (ob-asymptote.el), "simple-httpd"
(ob-js.el)... This is a non-issue for us, because it is inherent to Org
and thus cannot be solved by Org.

>From Glenn Morris: "Emacs already includes htmlfontify, since 23.2. Is
there some obstacle to Org using that?" This is begging for a specific
solution to a not-so-well defined problem. In any case, Kaushal Modi
answered this one. It is nice if this happens, but could we first define
correctly the problem so we can tell if this is the only possible
solution for it?

>From Richard Stallman: "To motivate people to do this, I say we should
not ship another release with that reference to GitHub." The issue
pointed out here seems to be that Org developers or enthusiasts are not
motivated enough to make Org use htmlfontify instead of htmlize. Note
this is very different from the initial report. Richard Stallman then
suggests a possible fix for that issue. It may or may not work; after
all these years spent in education, "motivating people" is a topic that
mostly eludes me. Anyway, since this point contains both the question
and the answer, I don't know what Org could do about it.

This is a genuine question: what /exactly/ do you want Org developers to
solve, assuming they can? Also, if they cannot, who is willing to give
them a hand?

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Nick Dokos]

Adam Porter  writes:

> I'm not an expert on this package nor this situation, however, looking
> at the htmlize.el file shows:
>
> ;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018
>
> So it would appear that the package has existed longer than either
> GitHub or Org.  I'm guessing that its author moved its primary repo to
> GitHub after Org started using it.
>
> In hindsight, perhaps it would have been better to move htmlize into
> Emacs before adding it to Org proper.  But many things are clearer in
> hindsight.
>
> Regardless of where it is hosted, htmlize.el is Free Software, and it's
> an optional addon to Org.  We can encourage its author to add it to
> Emacs proper, or to ELPA.  But surely it's not necessary to censor the
> mention of "GitHub" in the manual; it's simply a fact that GitHub exists
> and that htmlize.el is currently hosted there.  It would seem
> unreasonable for the Org maintainers to have reacted to htmlize.el's
> moving to GitHub by removing htmlize.el support while it remains Free
> Software, yet that's the logical conclusion of this argument.
>

I had exactly the same reaction.

> So please do not remove support for this package because of where its
> repo happens to be hosted at the moment.  That would be a major
> regression, and it would not be in users' best interests.  It would not
> be fair to remove a major feature used by thousands of users and demand
> that "someone" (since there is no one ultimately responsible) rewrite
> large parts of ox-html.el to fix it.  It would at least seem fair for
> those insisting on the change to do the necessary work.
>

I don't usually +1 replies but I wanted to chime in my agreement with
Adam here.  Thanks for taking the time to put your (and my!) thoughts
into words.

If Github is indeed the sticking point, why can't it (the htmlize
repo) be cloned on the same server as org-mode (possibly as its own
repo, possibly as a git submodule)? It's not a fast moving target: a
handful or two of commits per year. The doc can then avoid the Gihub
ref (although it does seem silly to pretend that Github does not
exist).

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Adam Porter]

I'm not an expert on this package nor this situation, however, looking
at the htmlize.el file shows:

;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018

So it would appear that the package has existed longer than either
GitHub or Org.  I'm guessing that its author moved its primary repo to
GitHub after Org started using it.

In hindsight, perhaps it would have been better to move htmlize into
Emacs before adding it to Org proper.  But many things are clearer in
hindsight.

Regardless of where it is hosted, htmlize.el is Free Software, and it's
an optional addon to Org.  We can encourage its author to add it to
Emacs proper, or to ELPA.  But surely it's not necessary to censor the
mention of "GitHub" in the manual; it's simply a fact that GitHub exists
and that htmlize.el is currently hosted there.  It would seem
unreasonable for the Org maintainers to have reacted to htmlize.el's
moving to GitHub by removing htmlize.el support while it remains Free
Software, yet that's the logical conclusion of this argument.

So please do not remove support for this package because of where its
repo happens to be hosted at the moment.  That would be a major
regression, and it would not be in users' best interests.  It would not
be fair to remove a major feature used by thousands of users and demand
that "someone" (since there is no one ultimately responsible) rewrite
large parts of ox-html.el to fix it.  It would at least seem fair for
those insisting on the change to do the necessary work.

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Eli Zaretskii]

> From: Richard Stallman 
> Date: Thu, 13 Sep 2018 22:55:15 -0400
> Cc: n...@flqt.fr, 32...@debbugs.gnu.org, m...@nicolasgoaziou.fr
> 
>   > >From what I remember, there is not objection to use that instead; it's
>   > just that someone has to work on converting ox-html to use htmlfontify
>   > instead of htmlize.
> 
> To motivate people to do this, I say we shouild not ship another
> release with that reference to GitHub.  Eli, do you agree?

This is an Org issue, so I would like to hear from Org developers
before I make up my mind.

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > >From what I remember, there is not objection to use that instead; it's
  > just that someone has to work on converting ox-html to use htmlfontify
  > instead of htmlize.

To motivate people to do this, I say we shouild not ship another
release with that reference to GitHub.  Eli, do you agree?


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

[Samuel Wales]

(htmlize-buffer-substring-no-invisible b e)

is this function available in emacs?

if not, it would be good to extract it and put it in emacs, or write
one for emacs.


On 9/13/18, Kaushal Modi  wrote:
> On Thu, Sep 13, 2018 at 11:28 AM Glenn Morris  wrote:
>>
>> Emacs already includes htmlfontify, since 23.2.
>> Is there some obstacle to Org using that? (bug#7506)
>
> This has been discussed before on the Org mailing list.
>
> From what I remember, there is not objection to use that instead; it's
> just that someone has to work on converting ox-html to use htmlfontify
> instead of htmlize.
>
>


-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.