Package: amarok
Version: 1.4.10-2
Severity: minor
Tags: patch l10n

In the "Track information" window there appear two different tabs titled
"Etiquetas". One for editing ID3 or Vorbis tags, and the other for attaching
arbitrary labels to a track, (for porpouses I haven't managed to grasp yet,
as there doesn't seem to be a way to search for tracks labelled one way or
another).

The first ones are stored in the actual file the track represents and are
composed of a name and a value. The second ones are stored internally by
amarok and are composed of just a name.
They are different and work differently; therefore, they should not both
be called "Etiquetas". In the original localization of amarok, they first
ones are called "tags" and the others are called "labels".

I propose to translate "labels" as "marcas", to differentiate them from
"tags", that should remain as "etiquetas", when reffering to those arbitrary
words the user can attach to a track.


-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages amarok depends on:
ii  amarok-common    1.4.10-2                architecture independent files for
ii  amarok-engine-xi 1.4.10-2                Xine engine for the Amarok audio p
ii  amarok-engine-ya 1.4.10-2                Yauap engine for the Amarok audio 
ii  kdelibs4c2a      4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for al
ii  libc6            2.7-18                  GNU C Library: Shared libraries
ii  libgcc1          1:4.3.2-1.1             GCC support library
ii  libgl1-mesa-glx  7.0.3-7                 A free implementation of the OpenG
ii  libglib2.0-0     2.16.6-1                The GLib library of C routines
ii  libgpod3-nogtk   0.6.0-6                 library to read and write songs to
ii  libifp4          1.0.0.2-3               communicate with iRiver iFP audio 
ii  libkarma0        0.0.6-4                 Rio Karma access library [runtime 
ii  libmtp7          0.2.6.1-3               Media Transfer Protocol (MTP) libr
ii  libmysqlclient15 5.0.51a-24              MySQL database client library
ii  libnjb5          2.2.5-4.2               Creative Labs Nomad Jukebox librar
ii  libpq5           8.3.6-1                 PostgreSQL C client library
ii  libqt3-mt        3:3.3.8b-5              Qt GUI Library (Threaded runtime v
ii  libruby1.8       1.8.7.72-3              Libraries necessary to run Ruby 1.
ii  libsdl1.2debian  1.2.13-2                Simple DirectMedia Layer
ii  libsqlite3-0     3.5.9-6                 SQLite 3 shared library
ii  libstdc++6       4.3.2-1.1               The GNU Standard C++ Library v3
ii  libtag1c2a       1.5-3                   TagLib Audio Meta-Data Library
ii  libtunepimp5     0.5.3-7                 MusicBrainz tagging library
ii  libusb-0.1-4     2:0.1.12-13             userspace USB programming library
ii  libvisual-0.4-0  0.4.0-2.1               Audio visualization framework
ii  unzip            5.52-12                 De-archiver for .zip files

Versions of packages amarok recommends:
pn  amarok-konqsidebar            <none>     (no description available)
ii  kdemultimedia-kio-plugins     4:3.5.9-2  enables the browsing of audio CDs 

Versions of packages amarok suggests:
pn  amarok-engines          <none>           (no description available)
ii  elinks [www-browser]    0.11.4-3         advanced text-mode WWW browser
ii  iceweasel [www-browser] 3.0.6-1          lightweight web browser based on M
ii  konqueror [www-browser] 4:3.5.9.dfsg.1-6 KDE's advanced file manager, web b
ii  libvisual-0.4-plugins   0.4.0.dfsg.1-2   Audio visualization framework plug
ii  lynx-cur [www-browser]  2.8.7dev9-2.1    Text-mode WWW Browser with NLS sup
pn  moodbar                 <none>           (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to