ehuelsmann / ledgersmb-book Goto Github PK

Need to investigate an easy way to move the figures closer to the relevant text.

Not sure if this is possible, but I thought that there was some automation in LedgerSMB that saved screen shots? If so, these should be pulled into this repo so the book is automatically updated.

For comparison the old roles were left in the appendix when he new auto generated roles were added. These need to be removed.

Apply the fixes used for style nextline in the new auto update roles appendix to the rest of the document.

I am struggling to make the PDF book title look good and still be acceptable in the multipage HTML. Something in the HTML generation is using the \title and \author on each page.

Need to figure out how to either limit it with HTML only tex or to configure the conversion to do something else.

AR > Reports > Customer History
AP > Reports > Vendor History
Although I payed with multiple combinations of the search filter, no record coming out in the report.
Is that a bug or Do I need to aware anything before generating report?

Reported by @aungzwin10 in ledgersmb/LedgerSMB#5194

The link referenced https://github.com/ledgersmb/LedgerSMB/blob/1.10/doc/reconciliation/recon_csv.pl

is not valid. It should be https://github.com/ledgersmb/LedgerSMB/blob/1.9/doc/reconciliation/recon_csv.pl

But of course, this whole section needs work.

Reported by @lifeboy on 30 May 2024

Need to update the book.

For example the definition of "type of business" will have the canonical definition appear in the API docs. This needs to be propagated to the book.

I think you want to short-cut the book section on Budgets the same way you did with Overpayments. They just don't work at the moment (and they're on my back-burner; we have enough code to be refactored as it is)

I think that we should change the order of the sections in chapter 1:

• Introduction (merge "release history" into this section?)
• Supported functionalities
• Feature comparison with alternatives
• System requirements
• Application architecture
• License

In chapter 3, there is:

which seems exactly the definitions we'd want to add to the glossary. @neilt: The question is: when to put them like this (and do we then include them in the glossary still) and when to put them in the glossary without putting them in-line.

Write a parser to retrieve the configuration file definitions and comments, then insert those comments into the correct place in the book (auto-generated latex).

See ledgersmb/LedgerSMB#7759 for the format example.

Pull the LedgerSMB.yaml file from https://github.com/ledgersmb/LedgerSMB/blob/master/doc/conf/ledgersmb.yaml so any user customizations would not be in the book.

The HTML book versions for 1.10 at book.ledgersmb.org are not building glossaries correctly. The following partial extraction shows as HTML and should not.

\makeglossaries\newacronym
anzsicANZSICAustralian and New Zealand Standard Industry Classification \newacronymapAPAccounts payable \newacronymAPIAPIApplication Programmer Interface \newacronymarARAccounts receivable \newacronymcgiCGICommon Gateway Interface \newacronymcoaCoAchart of accounts \newacronymCOGSCOGScost of goods sold \newacronymcsvCSVComma Separated Values \newacronymECAECAEntity Credit Account

Don't know if this relates to the problem or not, but when I build an image of Ubuntu Lunar to process the book I have to use texlive-latex-extra not texlive-latex-recommended. If I don't the pdflatex does not process the book correctly. It never gets to latexml.

I looked for errors in the build script and did not find any.

In the HTML, both single page and split page, the acronyms and glossary follows the legal section, but do not have any html links because they are not in the Table of Contents.

At first glance this appears to be an upstream LaTeXML issue, but more investigation or a workaround is needed.

In the PDF all glossary entry descriptions end with a period that is not in the source file.

In the HTML this period is missing.

This appears to be a bug with LaTeXML. Probably need to file bug report.

FYI, there are some problems with LaTeXML and expl3-code.tex which are known upstream and being worked on. Since I cannot test the conversion I have not updated the roles.

Fatal:too_many_errors:100 Too many errors (> 100)!
	at expl3-code.tex; line 32102 col 0 - line 32102 col 5
	In Core::Definition::Expandable[\??? Mat... /usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex; from line 10710 col 0 to line 10710 col 33
Conversion failed 101 errors; 1 fatal error (See /home/ledgerdev1/ledgersmb-book/ledgersmb-book.latexml.log) (reqd. 22m 47.63s)

Move the info at

Website account hierarchies

to the book.

\index{} in glossary entries do not work for either pdf or html. Remove all index entries in the glossary.tex file. See the beginning of glossary.tex for a more complete explanation.

In order to do this the ADR files which are in markdown format will have to be converted to LaTeX. LaTeXML does not accept the markdown package so they will have to be converted prior to LaTeXML processing. Probably during the import process.

If we improve the descriptions in the API documents, then these same descriptions should be made available in the Book.

The docs I am talking about are available at https://docs.ledgersmb.org/openapi/1.10.0/LedgerSMB-api.html using the "Download" button.

The download link blob:https://docs.ledgersmb.org/2681dfcf-8bab-4fae-88d2-4e43753aa950 seems to work, but I wonder if the UUID is static or not.

This involves getting the current actions to post process latexml or setting up a new docker image so that we have more control over the process.