Hi,
On 2025-10-23 00:36:55 +0200 Riccardo Mottola
<[email protected]> wrote:
(...)
This allowed me to use UTF-8 and to maintain readable text. It would
not be
the case with HTML entities, not very readable for a long User Guide.
But that is how you are supposed to write it if no explicit charset
is used,
encoding entities.
I don't have issues opening the help file in french it all comes out
fine, so
by magic it is working for me without charset fixes.
What file do you mean? The one provided within HelpViewer itself?
the libxml2 parser should go away if possible, to make the code
portable. I
wonder if the internal parser can be made respect charset and how.
Will look
at t.
Well, if it was standard html, only one directive in the header
document should do what is needed.
What is powered with the existent xlp is the legend within figures. We
should be aware to keep this functionality, maybe related to the
parser.
But as said, French stuff comes out fine for me.
Using UTF-8?
We could default to UTF-8 for convenience perhaps.
I think this the way modern systems go: we might not only think about
occidental languages.
Well help files are not books, perhaps similar. HelpViewer retains
the
interface. But I guess you are not going to put all help files in one
place,
but every application has its own help file in resources (Even
localized, if
that can be made work correctly).
Oh! you are right. Is there already a matter of checking an existent
help file from the menu command "Info > help" (#?) and if so, what
should be the normalized name of this expected help file? If we
provide L18N, how should be the hierarchy or the naming convention?
So perhaps just a fancy way of checking "recent files" could be fine.
Or a "bookmark" list.
I agree for that too.
Well, the release used within gs-desktop by Ondrej Florian (See:
https://github.com/onflapp/gs-desktop then in:
Applications/HelpViewer),
which is older, has the 'Search' feature still working while the
most
recent SVN seems to get lost.
He has made a lot of changes in the meanwhile... so maybe he
implemented it.
The code I started with has no search, index, bookhself or print
implemented.
They will come. I like the idea.
However, I am biting the teeth at the parser and rendering engine, it
is
broken in many places even when displaying the supplied Help example.
I fixed
things like being able to display tags! previously they were
double-parsed!
Or properlly resize. Or handle escaped characters properly (since you
should
entities... they should actually work cleanly)
I confirm I needed to add many " " to deal with rendering issues.
Other examples are broken.
Some issues come from GUI, but they are very subtle. I am trying to
compare
on mac, but there I need to reimplement things and it behaves even
differently.
Maybe related to css parser engine?
Patrick
--
Patrick Cardona - Pi400 - GNU/Linux aarch64 (Debian 13.1)
Xorg (1:7.7+24) - libcairo2 (1.18.4-1+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: AGNOSTEP
- MUA: GNUMail (1.4.0)
