linuxmint / linuxmint/xreader

Unimplemented Annotations

Open
#66 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

FEATURE REQUEST
Dominant language
C
Stars
283
Forks
82
PR merge metrics
No merged PRs in 30d

Description

The following output shows up, when opening the test file...
Many annotations are not implemented yet. Issue #31 shows a part of them already.

$ xreader Annotations.pdf 

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_FREE_TEXT, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_INK, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_HIGHLIGHT, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_LINE, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_POLYGON, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_STAMP, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_UNDERLINE, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

** (xreader:25216): WARNING **: Unimplemented annotation: POPPLER_ANNOT_CIRCLE, please post a bug report on Xreader bug tracker (https://github.com/linuxmint/xreader/issues) with a testcase.

TESTFILE:
Annotations.pdf

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the supplied Annotations.pdf with xreader to reproduce the warnings for the listed annotation types. Read issue #31 and inspect the existing annotation handling before defining the scope; completion should cover the reported types without the corresponding unimplemented-annotation warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.