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

Problem: Non-ascii characters in output cause Archivematica to fail some processes #1702

Open
5 tasks
sromkey opened this issue Jul 12, 2024 · 0 comments
Open
5 tasks
Assignees
Labels
Status: review The issue's code has been merged and is ready for testing/review. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Milestone

Comments

@sromkey
Copy link
Contributor

sromkey commented Jul 12, 2024

Expected behaviour

If one of the tools that Archivematica uses prints out non-ascii characters, Archivematica should be able to proceed with processing and not fail the process (unless the tool itself does actually fail the process)

Current behaviour

Archivematica will fail the process if this happens, even if the tool can successfully run outside of Archivematica and complete the process.

Steps to reproduce

In a recent example, a user was attempting to normalize a PDF to PDF/a using the default Ghostscript command. Because the output included the characters >>>> Microsoft� Office Publisher 2007 <<<< , Archivematica failed the normalization job.

Your environment (version of Archivematica, operating system, other relevant details)

Archivematica 1.15.1


For Artefactual use:

Before you close this issue, you must check off the following:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged (if applicable)
  • Details about this issue have been added to the release notes (if applicable)
@sromkey sromkey added Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result. triage-release-1.17 labels Jul 12, 2024
@sromkey sromkey added this to the 1.17.0 milestone Sep 9, 2024
@replaceafill replaceafill self-assigned this Sep 11, 2024
@replaceafill replaceafill added the Status: in progress Issue that is currently being worked on. label Sep 11, 2024
@replaceafill replaceafill added Status: review The issue's code has been merged and is ready for testing/review. and removed Status: in progress Issue that is currently being worked on. labels Sep 12, 2024
@replaceafill replaceafill removed their assignment Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: review The issue's code has been merged and is ready for testing/review. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Projects
None yet
Development

No branches or pull requests

2 participants