yikes yes re columns.
[my fill-column is 60. on a 32 inch. and i cannot even do ediff side
by side with that, to my displeasure.]
[i hope to find a low-[preferably-1-nit]-minimum-brightness
flicker-free monitor someplace, and i /think/ oleds, which /might/
partly satisfy that, can come standard
On 05/08/2023 10:22, Samuel Wales wrote:
[i.e. agree that the manuals and standard toc at top imo do a good job
for accessibility.]
Notice that Org manual is exported through ox-texinfo, not by ox-html
directly. So somebody should confirm that default ox-html table of
contents is suitable for
rg exports? Org and Emacs manuals, with no
>>> "smart" side bars, get it right, IMO.
>>
>> I have found your message in a dedicated thread
>>
>> Rudolf Adamkovič to emacs-orgmode… Re: [accessibility] worg obscures
>> text. Sun, 12 Jun 2022 21:35
or me, in one way or
>> another. Why cannot TOC be included at the
>> beginning of the document, like in standard
>> Org exports? Org and Emacs manuals, with no
>> "smart" side bars, get it right, IMO.
>
> I have found your message in a dedicated thread
&
thank you. classic works best for me. a tiny bit made for smaller
fonts [perhaps ragged right or 1 column would work better] but it is
completely usable and i would not mention such a nit except for your
interest.
[as an indicator of right column column width in classic page style,
with smallest
Samuel Wales writes:
> on this page, i cannot read the rhs of paragraphs near the top because
> the menu and up home elements obscure the text.
> https://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development
> .
>
> i use very large fonts. i have latest esr fire
On 13/06/2022 09:16, Tim Cross wrote:
If the .emacs.el was either in the repo or the url referenced in the
worg-setup.org file worked, that would help.
Org web pages are currently generated by SourceHut CI, have a look at
.build.yml and publish.sh (the latter is actually elisp).
Browser deve
Ihor Radchenko writes:
> Tim Cross 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://g
Tim Cross 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 shi
Samuel Wales writes:
> on this page, i cannot read the rhs of paragraphs near the top because
> the menu and up home elements obscure the text.
> https://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development
> .
>
> i use very large fonts. i have latest esr fire
Samuel Wales writes:
> so i am just reporting so that the issue is known. i blieve i
> mentioned it yers ago but idk if it got notated.
A big +1 from me. I struggle with this problem too. The website
obscures its main content with the floating side-buttons, namely
- "Support via Liberapay",
11 matches
Mail list logo
