File: docs.txt

package info (click to toggle)
puddletag 1.2.0-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 15,640 kB
  • ctags: 3,062
  • sloc: python: 47,327; xml: 943; makefile: 129; sh: 84
file content (50 lines) | stat: -rw-r--r-- 1,516 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
.. include:: checksums.txt

puddletag Documentation
-----------------------

**Download these docs:** |docs_html_link|_ | |docs_rst_link|_

First I have to introduce you to the naming conventions used by puddletag (some copied from Mp3tag).

Say you have a MP3 file with full path /mnt/music/Miley - Cyrus/USA Party.mp3

+   The container used to store metadata will be referred to as the tag. In this case it's like an ID3 tag. All containers are referred to as tags. So when I say tag think complete as APEv2 tag, ID3 (ID3v2, ID3v1) tag, etc.
+   Fields are what the different attributes of the file are called. Eg. **artist, title** or **album**.
+   Values associated with fields are referred to as...'values' (like 'Miley Cyrus' or 'USA Party' ). If there's more than one value associated with a field (eg. two genres) it'll referred to as a multiple-valued field.
+   Sometimes I use **tag** to refer to the all the fields + values contained in a file.

Tutorials
---------

.. toctree::
    :maxdepth: 1

    source/tut1
    source/tut2
    Things you should know (like how to add album art) <source/tut3>
    source/tut4
    source/tut5

Reference
---------
.. toctree::
    :maxdepth: 1

    source/menus
    Functions <source/function>
    Scripting Functions <source/scripting>
    source/filter
    Tag Sources <source/tagsources>
    Preferences <source/preferences>
    source/id3
    source/tags
    

Development
-----------
.. toctree::
    :maxdepth: 1
    
    source/plugins
    source/translate