Age | Commit message (Collapse) | Author |
|
|
|
# Conflicts:
# CMakeLists.txt
# res/lang/cs.bin
# res/lang/de.bin
# res/lang/en.bin
# res/lang/eo.bin
# res/lang/es.bin
# res/lang/es_MX.bin
# res/lang/fi.bin
# res/lang/fr.bin
# res/lang/gl.bin
# res/lang/hu.bin
# res/lang/ia.bin
# res/lang/ie.bin
# res/lang/isv.bin
# res/lang/nl.bin
# res/lang/pl.bin
# res/lang/ru.bin
# res/lang/sk.bin
# res/lang/sr.bin
# res/lang/tok.bin
# res/lang/tr.bin
# res/lang/uk.bin
# res/lang/zh_Hans.bin
# res/lang/zh_Hant.bin
|
|
|
|
Solderpunk's November 2021 update to the specification included a recommendation to normalize empty paths to /.
IssueID #455
|
|
|
|
Omit the actual data.
|
|
|
|
|
|
With Gopher, ensure that the item type changes to 1, and with Titan, change to normal Gemini.
|
|
Making URL encoding a little less convoluted. Now when sending out a request, the URL is fully encoded except for reserved characters. In the internal representation, non-ASCII characters are in decoded form (i.e., IRI).
This means that if the user enters a URL in the input field manually, its non-ASCII characters will be percent encoded as well. However, in this case the user is expected to manually escape all reserved characters because the input field can't tell the difference between what is intended to be a reserved separator and what isn't. For example, a server might expect &-separated fields, and if the user enters such fields manually in the URL field, they shouldn't be converted to %26.
When forming a query URL in the input dialog, user-entered text is fully percent-encoded because in that case the input is just a generic text string.
IssueID #410
|
|
Manage a color palette separately for each GmDocument, and activate one of them globally whenever a document is being drawn.
Palettes are cached in memory.
|
|
|
|
# Conflicts:
# CMakeLists.txt
# Depends.cmake
# src/lang.c
|
|
The Gemini specifications says to encode RFC3986's reserved characters in URLs, but that didn't apply to plus characters in the "canonical" form.
|
|
|
|
|
|
Warn the user about missing glyphs and potentially unsupported ANSI escapes.
TODO: Site-specific setting for dismissed warning; fonts preference about missing glyph warnings.
|
|
Be more robust in `init_Url()`.
|
|
|
|
Convert Markdown to Gemtext and use ANSI escape sequences to switch fonts (bold, italic, monospace). The conversion is still a bit buggy...
|
|
Media still needs more work to get rid of redundancies and make lookups faster.
FontPacks are manipulated as Media items (not unlike images) so they can be previewed on page, and installed via a click.
FontPack management is not trivial as it includes such details as versioning and whether individual packs are enabled or disabled.
|
|
Three important changes:
1) Visited URLs can be marked as "kept" so they will never be discarded due to old age.
2) Feed entries are not discarded from the database until they are removed from the source, and then become too old (six months).
3) Visited feed entry URLs are always flagged as kept, so the (un)read status will not be forgotten.
|
|
The handling of colons (a reserved character used in the URL scheme and authority) was left ambiguous in the canonical form.
|
|
# Conflicts:
# CMakeLists.txt
# res/about/version.gmi
|
|
|
|
|
|
|
|
The user is able to ignore certificate expiry and continue loading the page regardless. This adds a one hour exception to the expiration date.
|
|
If a server sends a different certificate (checked by matching public key fingerprints), abort the connection at the TLS handshake stage.
A new error page is shown explaining the situation. A button is provided for conveniently opening Page Information, where trust can be updated.
The file format of "visited.txt" was updated, so it is now called "visited.2.txt". The new format includes server port numbers, and the fingerprints are calculated based on public keys.
IssueID #308
IssueID #309
IssueID #310
|
|
|
|
|
|
Internally, all URIs should be converted to a canonical form so that they can be compared against each other.
The canonical form is an IRI with spaces and reserved characters percent-encoded.
|
|
When a page is opened from the sidebar, swiping back will now reopen the sidebar. Another swipe will dismiss the sidebar and navigate back as usual.
Attempted to cache theme colors in GmDocument, but there were issues with theme changes.
|
|
Opening an URL or making a search query from the command line.
IssueID #232
|
|
Exporting an identity will display it in a new tab in PEM encoded format, where it can be saved or copied.
IssueID #236
|
|
`GmRequest` should use the correct path separators on Windows in
native paths.
|
|
IssueID #269
|
|
When opening a Gempub, split the window and show the index page and the first chapter.
|
|
`Gempub` opens and parses a Gempub archive and provides access to the contents in a common way.
|
|
An equals sign has no special meaning in the path part of an URL, so encoding it always is unnecessary.
Fixes apparent URL decoding issue on gemini://gemif.fedi.farm/ .
|
|
Use MIME hooks to generate a Gempub cover page with a preloaded cover image.
This required applying MIME filtering to "file://" requests as well.
Todo: More cleanup, add a gempub.c.
|
|
One is now able to view directory and ZIP archive contents using file URLs.
Directory contents are shown as a list of links, enabling previewing supported formats. A link to the parent directory is included at the top of the page.
ZIP archives behave like directories, except they also recognize "index.gmi" and "index.gemini" files and display them instead of the regular directory index (when viewing a directory inside a ZIP archive). This enables archiving a Gemini capsule and browsing it as a ZIP archive.
Added a preference to disable loading of index pages.
|
|
|
|
The brackets that were removed must be put back if needed.
|
|
The brackets are part of the URL notation and should not be considered part of the IPv6 address itself.
|
|
IssueID #226
|
|
IssueID #215
|
|
IssueID #192
|
|
Couple of problems:
- "data:" links were not flagged as supported
- "data:" links are not supposed to further decoded or encoded since
they are processed internally in the client
IssueID #217
|
|
Dashes may appear in domain names.
|