Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: exporting pdf-tm Non-built-in style display absolute path #1272

Open
tangdouer1005 opened this issue Oct 18, 2023 · 6 comments
Open

bug: exporting pdf-tm Non-built-in style display absolute path #1272

tangdouer1005 opened this issue Oct 18, 2023 · 6 comments
Labels
bug Something isn't working plugin:PDF

Comments

@tangdouer1005
Copy link
Contributor

Mogan 版本

1.2.0 beta28

操作系统版本和架构

macos

描述问题

If the user uses a non-built-in style and then opens the pdf-tm after exporting the pdf-tm, the style will be displayed incorrectly.

期待的结果

display style correctly

@tangdouer1005 tangdouer1005 added the bug Something isn't working label Oct 18, 2023
@da-liii
Copy link
Contributor

da-liii commented Oct 21, 2023

I suggest that you should fix this bug first and then start to port the code from Mogan to GNU TeXmacs.

@mgubi
Copy link
Contributor

mgubi commented Mar 12, 2024

I would like to help with the TeXmacs port of the project. What is the current status? I start to badly need this feature working in TeXmacs. :) Fixing for non-standard style file could be quite complex, as it means importing arbitrarily nested styles and packages. Moreover these style files could depend on scheme scripts which would not be importable/usable from the pdf-tm. So it is not clear what a correct fix is. In some sense it is not a problem of pdf-tm but a lacking feature of TeXmacs: make documents independent of the surrounding environment. The clean solution so far should be to detect the problem and warn the user that the tm-pdf file still depends on outside content which has to be present in order for the file to render correctly.

@da-liii
Copy link
Contributor

da-liii commented Mar 12, 2024

The only annoying bug is that it only works for PDF 1.4, if one switched the PDF version to 1.5/1.6/1.7, it will fail to attach the tm document to PDF without any warning or error.

@mgubi
Copy link
Contributor

mgubi commented Mar 13, 2024

What is the problem? where the program fails and how I can test the problem? I've adapted the code for TeXmacs and I'm preparing a PR here: https://github.com/texmacs/texmacs/tree/wip_pdftm

@mgubi
Copy link
Contributor

mgubi commented Mar 13, 2024

I've also modified a bit the embedding code, since the version in Mogan does not embed the bibliographic data in the original document. (both attachments and auxiliary elements of the document)

@da-liii
Copy link
Contributor

da-liii commented Mar 14, 2024

What is the problem?

In Edit->Preferences->Convert->Pdf->Pdf version number, set it to 1.5, 1.6 or 1.7, the exported PDF does not contain the texmacs document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working plugin:PDF
Projects
None yet
Development

No branches or pull requests

3 participants