emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [accessibility] worg obscures text
Date: Mon, 13 Jun 2022 12:16:36 +1000	[thread overview]
Message-ID: <87tu8puwlt.fsf@gmail.com> (raw)
In-Reply-To: <87mteh4d0b.fsf@localhost>


Ihor Radchenko <yantar92@gmail.com> writes:

> Tim Cross <theophilusx@gmail.com> writes:
>
>> I agree, that is pretty poor formatting and does not work well and will
>> never work well from an accessibility perspective.  
>
> Patches are welcome! We just need someone with knowledge of html/css to
> jump in and create a patch for https://git.sr.ht/~bzg/worg (BTW, also
> see shiny new https://sr.ht/~bzg/org/).
>

Sadly, it isn't that simple. You also have to understand how worg does
the publishing and that isn't easy. I just looked at the repository 

- The .emacs.el file referenced in the worg-setup.org is not available (404 error)
- The styles directory consists of a number of css files - not clear
  which one is used. (I'm guessing the .emacs.el file might tell me such
  details). 
- You also need to know about org publish and how it works, not just be
  familiar wiht html and css. 
  
As it stands now, without the .emacs.el file (which I'm assuming
contains the org-publish-project-alist variable), you cannot do much or
work out how the styles are generated/applied, so you cannot fix this. 

If the .emacs.el was either in the repo or the url referenced in the
worg-setup.org file worked, that would help. 


  reply	other threads:[~2022-06-13  2:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13  0:22 ` Tim Cross
2022-06-13  0:34   ` Ihor Radchenko
2022-06-13  2:16     ` Tim Cross [this message]
2022-06-13  5:30       ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13  5:44         ` Tim Cross
2022-06-13  6:14           ` Timothy
2022-06-13 14:21           ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 14:21         ` Bastien Guerry
2022-06-13 22:32           ` Tim Cross
2022-06-14  0:57             ` Ihor Radchenko
2022-06-14  1:08               ` Tim Cross
2022-06-14  1:37                 ` Ihor Radchenko
2022-06-14  1:51                   ` Tim Cross
2022-06-14  2:18                     ` Ihor Radchenko
2022-06-14  2:46                       ` Tim Cross
2022-06-14  2:59                         ` Ihor Radchenko
2023-01-02 10:40                 ` Ihor Radchenko
2023-01-02 20:03                   ` Tim Cross
2023-01-03 11:01                     ` Ihor Radchenko
2023-01-04 10:21                     ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50                       ` Alain.Cochard
2023-01-04 22:43                         ` Tim Cross
2023-01-05 14:07                           ` Alain.Cochard
2023-01-05 15:41                             ` Tim Cross
2023-01-05 20:18                               ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06  1:23                                 ` Tim Cross
2022-06-13  5:37       ` [accessibility] worg obscures text Max Nikulin
2022-06-16  3:22 ` Tim Cross
2022-06-16 23:30   ` Samuel Wales

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87tu8puwlt.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).