randogoth/orvanitag
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: add tagspaces plugin with folder and any-file-type plugin support

Browse source
This commit is contained in:
randogoth 2026-10-25 10:32:22 +02:00
parent 712fe264be
commit 4cfbd581bc
6 changed files with 225 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -93,7 +93,7 @@ $ otag purge old-project/
### Embedded Metadata
`scan` (`s`) reads tags that are embedded in files and adds them to their entries, in the given folder (default: current) and its subdirectories. `--replace` makes the found tags replace the entry instead, so tags removed in another app also disappear from otag; files without embedded tags keep their entry.
`scan` (`s`) reads tags that are embedded in files and adds them to their entries, in the given folder (default: current) and its subdirectories. Plugins that support folders, like `tagspaces`, also read the subfolders' tags. `--replace` makes the found tags replace the entry instead, so tags removed in another app also disappear from otag; files without embedded tags keep their entry.
`write` (`w`) writes the entry of a file into the file itself, using the named plugin. It replaces what the plugin stored before, so tags removed with `otag remove` disappear from the file on the next `write`. `-c` (`--clear`) removes the plugin's tags from the file instead, e.g. after all tags were removed; it is never done implicitly, because a file without entry may also be one otag never tagged.
@ -108,6 +108,7 @@ $ otag write --clear id3 song.mp3
| `id3` | `.mp3` `.wav` `.flac` `.ogg` | The comment tag |
| `image` | `.jpg` `.jpeg` `.png` `.gif` | An `otag:` comment of its own next to any other comments: a COM segment in JPEG (after the JFIF and EXIF segments; some apps only show a JPEG's last comment), an iTXt `Comment` chunk in PNG, a comment extension in GIF (turning a GIF87a into GIF89a). The image data stays unchanged |
| `pdf` | `.pdf` | The keywords field |
| `tagspaces` | Every file type and folders | The JSON sidecar [TagSpaces](https://www.tagspaces.org) uses: `.ts/<name>.json` next to a file, `.ts/tsm.json` inside a folder. Tags are written bare as in TagSpaces, projects and contexts keep their `+` and `@`; spaces in TagSpaces tags become `_`. Tags in a file name like `photo[vacation alps].jpg` are read but never written, since that would rename the file. The note and the sidecar's description, colors and other data are left untouched |
| `office` | `.docx` `.xlsx` `.pptx` `.odt` `.ods` `.odp`, reading also `.doc` `.xls` `.ppt` | The description field |
| `ebook` | `.epub` `.fb2` `.cbz` | One otag line where other apps don't look: a `<meta name="otag">` in the EPUB package file, a `<custom-info info-type="otag">` in FB2, the archive comment of CBZ (never overwriting another tool's comment); the book's own metadata is left untouched |
| `archive` | `.zip` `.tar` `.gz` `.tgz` (so also `.tar.gz`) | An `otag:` comment that unpacking ignores: the archive comment of ZIP, the comment field of the gzip header, a pax global header at the start of a tar. Another tool's comment, like the commit id stored by `git archive`, is never replaced. Writing a tar or gzip file copies it once, the packed data stays unchanged |