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

PDF - large table #4273

Open
pengchenglai opened this issue Jan 27, 2025 · 5 comments
Open

PDF - large table #4273

pengchenglai opened this issue Jan 27, 2025 · 5 comments
Labels
enhancement New feature or request

Comments

@pengchenglai
Copy link
Contributor

pengchenglai commented Jan 27, 2025

@minotogna

Describe the bug
Some data gets lost when there is a large table.
To Reproduce
Example

  1. Cyprus PDF:
    Go to table 2a

  2. Denmark / Syrian Arab Republic / North Macedonia /Haiti
    Table 1a & 1b, NDP

Screenshots
Cyprus:
Image

Image

Denmark:

Image

@pengchenglai
Copy link
Contributor Author

@minotogna

Do you have any suggestions? One possible solution proposed is to keep only the FRA years(such as 1990, 2000 ......) for the NDP issue (Table 1a &/ Table 1b).

@pengchenglai
Copy link
Contributor Author

In cases such as in Cyprus, where a user has entered a large table in section 2a Estimation and Forecasting, one possible solution could be to adjust the column width for the years (2010, 2011, 2015, 2020, 2021, 2022, 2023, 2024, 2025) and align the numbers to the left or right, or make the table font smaller.

Image

@minotogna
Copy link
Member

@pengchenglai we can control only our tables, not free text content as it is not structured.
this problems will always happen if we let users enter whatever they want and be included in the print.
This kind of information should be entered as attached files and be included as annex. But this is not happening atm .

We can analyze and try to fix the cases (you have mentioned in this issue) by altering the user entered content in order to adjust the data. But this is not a solution, but we can try, if you want

@minotogna minotogna added the enhancement New feature or request label Mar 5, 2025
@pengchenglai
Copy link
Contributor Author

@minotogna

Yes, we need to separate this issue into two circumstances:

  1. Structured tables with too many columns. The Admin has kindly agreed to keep the FRA years for the simplicity of life, as it preserves the trend and the most important information.
  2. Plz give it a shot. No, it is not the best solution, but we could set up some limitations for the upcoming assessments when users enter the tables (e.g., a maximum of 10 columns; otherwise, users will have to upload the table as an annex and attach the link).

@minotogna
Copy link
Member

@minotogna

Yes, we need to separate this issue into two circumstances:

  1. Structured tables with too many columns. The Admin has kindly agreed to keep the FRA years for the simplicity of life, as it preserves the trend and the most important information.
  2. Plz give it a shot. No, it is not the best solution, but we could set up some limitations for the upcoming assessments when users enter the tables (e.g., a maximum of 10 columns; otherwise, users will have to upload the table as an annex and attach the link).

@pengchenglai could you please clarify :

  1. Structured tables: ALL tables should contain only FRA years ? 1990, 2000, 2010, 2015, 2020, 2025?
  2. I'm not sure I fully understand.
  • Should we try to alter the user content ?
  • We Cannot control user content, therefore we cannot control how many columns they enter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants