From: Juliano David Hilario <yellowcutterpillow@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Offline documentations
Date: Mon, 2 Oct 2023 16:37:35 +0800 [thread overview]
Message-ID: <CACa+7H8gp2zwOAG4T2Dcn4ta5fxP-d5PJUCQZtamwUNw73Ju9A@mail.gmail.com> (raw)
In-Reply-To: <CACa+7H8tfTtzX-3JaSso7PP4mFtuJtwRdyBucoC5qSk6y4aMrw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2460 bytes --]
Also, if I were to do that, I might just make at the moment some sort of
search engine, or grep it when I need something, then view whatever I need
in the wiki. I'm just wondering if it's fine if I were to send many GET
requests and obtain a copy of the wiki. Would that act like a DDoS attack?
On Mon, Oct 2, 2023, 4:32 PM Juliano David Hilario <
yellowcutterpillow@gmail.com> wrote:
> If I were to download the entire wiki with the exception of the discussion
> files and the user pages, do you think it would be wise? I would try to
> make it dynamically updatable too, if possible, and also try to make as
> offline-friendly as the Python docs. Do you think that would be wise? Thank
> you for your help, the wiki is very useful.
>
> On Mon, Oct 2, 2023, 4:29 PM Henning Hraban Ramm <texml@fiee.net> wrote:
>
>> Am 02.10.23 um 09:59 schrieb Juliano David Hilario:
>> > Is there a way to view the documentations offline? Sort of the way the
>> > Python docs work, where you could just search for a subject and it will
>> > function regardless of internet connection. If it's not yet working, I
>> > could contribute some of my time if it's not that a heavy of a task.
>> > Something like this would be convient, since some like to search by
>> > topic. Though since we probably have the common ground of liking
>> > writing, we, or most of us, prefer referring to current manuals out
>> there.
>>
>> Well, the documentation is spread over several PDF files, and the wiki
>> is not usable offline, of course.
>>
>> You can grep through the sources of the manuals (in
>> texmf-context/doc/context/sources).
>>
>> And there is a command reference browser:
>>
>> mtxrun --script server --auto
>>
>> and the open
>> http://localhost:8088/mtx-server-ctx-help.lua
>>
>> But since it just shows what’s in the interface files, it lacks any
>> explanations.
>>
>> Hraban
>>
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to
>> the Wiki!
>>
>> maillist : ntg-context@ntg.nl /
>> https://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
>> archive : https://bitbucket.org/phg/context-mirror/commits/
>> wiki : https://contextgarden.net
>>
>> ___________________________________________________________________________________
>
>
[-- Attachment #1.2: Type: text/html, Size: 3769 bytes --]
[-- Attachment #2: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-10-02 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACa+7H8kYq4QtBnb-cJN2DQokYfYZddkqH5RpqNHzm-o_RT2_Q@mail.gmail.com>
2023-10-02 7:59 ` [NTG-context] " Juliano David Hilario
2023-10-02 8:24 ` [NTG-context] " Henning Hraban Ramm
2023-10-02 8:32 ` Juliano David Hilario
2023-10-02 8:37 ` Juliano David Hilario [this message]
2023-10-02 8:55 ` Henning Hraban Ramm
2023-10-02 9:07 ` Hans van der Meer via ntg-context
2023-10-02 15:57 ` Juliano David Hilario
2023-10-02 8:47 ` Henning Hraban Ramm
2023-10-02 8:57 ` Thomas A. Schmitz
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=CACa+7H8gp2zwOAG4T2Dcn4ta5fxP-d5PJUCQZtamwUNw73Ju9A@mail.gmail.com \
--to=yellowcutterpillow@gmail.com \
--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).