GNU Astronomy Utilities - Tasks: task #16297, Add "How to read this...
You are not allowed to post comments on this tracker with your current authentication level.
task #16297: Add "How to read this manual" section in the book
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Tue 20 Dec 2022 02:40:48 PM UTC | ||
Should Start On: | Tue 20 Dec 2022 12:00:00 AM UTC | Should be Finished on: | Tue 20 Dec 2022 12:00:00 AM UTC |
Category: | Book | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | Postponed |
Privacy: | Public | Percent Complete: | 0% |
Assigned to: | makhlaghi | Open/Closed: | Open |
Effort: | 0.00 |
Fri 23 Dec 2022 08:37:28 AM UTC, comment #4: |
Pedram Ashofteh-Ardakani <pedram>![]() |
Fri 23 Dec 2022 08:19:28 AM UTC, comment #3: Oops, don't mind the previous info.jpg, here is the new one (file new-info.jpg) |
Pedram Ashofteh-Ardakani <pedram>![]() |
Fri 23 Dec 2022 08:14:44 AM UTC, comment #2: Another note: most likely, we do not need to add unicode characters in the 'texi' file. They are not readable in the source code. But using the programming glyphs will be readable.
|
Pedram Ashofteh-Ardakani <pedram>![]() |
Thu 22 Dec 2022 05:42:01 PM UTC, comment #1: Indeed this would be a more friendly introduction for newcomers.
|
Pedram Ashofteh-Ardakani <pedram>![]() |
Tue 20 Dec 2022 02:40:48 PM UTC, original submission:
The Gnuastro book has become very extensive (843 pages in version 0.19). This can make it hard for someone new to Gnuastro to get a generic and high-level idea of how to read it.
|
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 10 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-12-23 | pedram | Attached File | - | ![]() |
Added utf8-info.jpg, #54159 |
Attached File | - | ![]() |
Added utf8-pdf.jpg, #54160 | ||
Attached File | - | ![]() |
Added utf8-html.jpg, #54161 | ||
2022-12-23 | pedram | Attached File | - | ![]() |
Added new-info.jpg, #54158 |
2022-12-23 | pedram | Attached File | - | ![]() |
Added html.jpg, #54155 |
Attached File | - | ![]() |
Added info.jpg, #54156 | ||
Attached File | - | ![]() |
Added pdf.jpg, #54157 | ||
2022-12-23 | pedram | Carbon-Copy | Removed -email is unavailable- | ![]() |
- |
2022-12-20 | makhlaghi | Carbon-Copy | - | ![]() |
Added -email is unavailable- |
Carbon-Copy | - | ![]() |
Added -email is unavailable- |
Oh we can actually use the UTF-8 characters in texinfo with the @U{HEX-NUMBER-HERE} instruction. We can also define MACROs for things we need that aren't there by default. For example, the \leftarrow in my previous screenshots can be produced by @U{2190}. The output looks the same in the pdf, but it actually prints a '←' in the 'info' and 'html' versions instead of a lame '\leftarrow'.
For example:
and then simply:
Which will produce a beautiful left arrow in pdf, html, and the info.