gmane.linux.debian.devel.debtags

Calendar management-related tags

Tanguy Ortolo — 2012-02-28T17:04:05

Hello,

I think it would be useful to define the following tags:
    works-with::calendar            calendar data
    works-with-format::icalendar    iCalendar (RFC 5545)
    protocol::webcal                WebCAL, that iCalender exposed by
                                    HTTP
    protocol::caldav                CalDAV (RFC 4791)

Indeed, I think the only related tag, use::timekeeping, is far from
being useful enough when searching for a software. For instance, a
common requirement would be to be able to import iCalendar files.
Someone using a remote calendar server would also want a CalDAV support,
etc.

By the way, the rationale for having protocol::webcal and
protocol::caldav instead of simply protocol::http is that these are two
HTTP-based protocols that are quite different, and often used for
distinct purposes.

Regards,

Tags for region and translation status?

Michael Vogt — 2012-02-13T10:22:38

Hi,

when discussing about how to classify software better two ideas came
up and I would like to ask for you opinions about them.

One is to have a "region::" tag that would include the rfc3166
regions. The meaning would be something like "useful mainly in this
region". This could be e.g. a german tax application that is specific
to the german tax law. Or a IM client that is used 99% in china. Or a
english train table travel planer. The use-case would be that e.g. in
software-center there would be a gentle warning that the app may not
be useful in your current region. It could also be used to alter
search results (e.g. region::cn and searching for IM). I know there is
the culture:: tag, but it seems to not quite match the above plus its
not granular enough for e.g. the tax application use-case (as
culture::german is too broad and includes other german speaking
countries with different tax laws).

The other one (probably more controversial as this will clutter the
Tags file a lot) is to include a translated::$lang tag when there is a
translation for the app (or when more than e.g. 80% are
translated). This would be useful to e.g. hide (or warn about)
untranslated apps for the current users language. I'm not 100%
convinced about this one myself as it will potentially increase the
size of the tags quite a bit (but I guess I should actually measure
this). But I would really like the feature :)


If there is approval about the idea I'm happy to implement a client
lib/command similar to the new debtagshw/debtags-hardware work.

Feedback about the above ideas are very welcome!

Cheers,
 Michael

please add "devel::lang:vala" tag

Sebastian Reichel — 2012-01-28T12:00:55

Hi,

IMHO all vala development related tools should be tagged as
"devel::lang:vala", but there is no such tag yet. Can you
add it please?

Added new system::* debtags facet

Enrico Zini — 2012-01-28T15:32:28

Hello,

I have finally added the new system::* facet to the Debtags vocabulary:
http://debtags.debian.net/reports/facets/system

This is the bit of vocabulary[1] that has been added:

  Facet: system
  Description: Class of system
   Class of system a package provides specific functionality for.
 
  Tag: system::cloud
  Description: Cloud
   Cloud computing is the delivery of computing as a service rather than
   a product, whereby shared resources, software, and information are
   provided to computers and other devices as a metered service over a
   network (typically the Internet).
   .
   Link: http://en.wikipedia.org/wiki/Cloud_computing
 
  Tag: system::embedded
  Description: Embedded
   A computer system designed for specific control functions within a larger
   system.
   .
   Link: http://en.wikipedia.org/wiki/Embedded_system
 
  Tag: system::laptop
  Description: Laptop
   A personal computer for mobile use.
   .
   Link: http://en.wikipedia.org/wiki/Laptop
 
  Tag: system::mobile
  Description: Mobile device
   A small, hand-held computing device, typically having a display screen with
   touch input and/or a miniature keyboard.
   .
   http://en.wikipedia.org/wiki/Mobile_device
 
  Tag: system::server
  Description: Server
   A physical computer (a computer hardware system) dedicated to
   running one or more such services (as a host),[1] to serve the needs
   of users of the other computers on the network. Depending on the
   computing service that it offers it could be a database server, file
   server, mail server, print server, web server, or other.
   .
   Link: http://en.wikipedia.org/wiki/Server_(computing)
 
  Tag: system::virtual
  Description: Virtual
   A virtual computer hides the physical characteristics of a computing platform
   from users, instead showing another abstract computing platform.
   .
   Link: http://en.wikipedia.org/wiki/Hardware_virtualization
 
  Tag: system::TODO
  Description: Need an extra tag
   The package can be categorised along this facet, but the right tag for it is
   missing.
   .
   Mark a package with this tag to signal the vocabulary maintainers of cases
   where the current tag set is lacking.
 

If you feel like something should be improved, please send patches
against the vocabulary file at:
http://anonscm.debian.org/viewvc/debtags/vocabulary/trunk/debian-packages?view=markup

Please note, if you are considering improving descriptions, that I would
prefer them to be Wikipedia extracts whenever possible, so please
improve them in Wikipedia first :)

 
Ciao,

Enrico

Vocabulary additions

Samuel Bronson — 2012-01-28T00:23:56

I'm proposing a few things for addition to the debtags vocabulary:

* devel::lang:erlang and implemented-in::erlang, for Erlang stuff

* devel::lang:vhdl, for VHDL tools

* devel::lang:verilog, for Verilog tools

* devel::lang:TODO, for development tools for languages that do not yet
  have their own "devel::lang:" tag.

* works-with-format::diff, for tools that work with diff-format
  patches. (Now if only we could apply debtags to commands and
  subcommands within a package, then we could tag stuff like "git diff"
  and "git am"...)

I have a debtags patch to justify all but the Erlang tags and
devel::lang:TODO; there are LOT of erlang-related packages, and TODO
tags are rather meta.

Feedback on a new system::* set of tags

Enrico Zini — 2012-01-24T10:36:47

Hello,

I proposed a new set of tags to show what class of system a program is
specific for. The full proposal is at:
http://lists.alioth.debian.org/pipermail/debtags-devel/2012-January/002157.html

The proposal contains a definition of 'embedded' that I took from
Wikipedia, and a question about smartphones vs tablets.

Can I have your feedback on that proposal?


Ciao,

Enrico

Tags in control files

Enrico Zini — 2012-01-21T23:21:11

Hello,

debtags tracks tags by package name, regardless of package version. That
is generally fine, except when packages get renamed, and we are using
the same set of tags for all releases (stable, testing and unstable).
Think git and chromium, for example.

Seemingly unrelated, some maintainers have asked me for a way to say
"tags on this package are final, please don't change them anymore".

A way to solve both problems is this: allow a maintainer to add a "Tag"
header in debian/control for some binary packages. If the Tag header
exists, that is authoritative; otherwise, the overrides are used.

By default, people would NOT add Tag headers to their debian/control.
However, if one wishes to have different tags for different versions of
a package, or if one prefers to have the tags of some of their packages
maintained over the BTS instead of the debtags.debian.net workflow, then
they are free to choose to do so.

AFAICT, however, this needs coordination with ftp-master. At the moment,
unless I am mistaken, the overrides I provide would overwrite a Tag:
header from debian/control, but what I'm looking for is to have the Tag:
header have priority over the overrides.

I could drop the overrides for packages that have tags in
debian/control, but that would mean dropping the overrides for any
version of the package, including old ones which instead would benefit
from the overrides.

Alternatively I could import tags from control files into the overrides,
but that would mean that the tags from one version of the package are
still used for all versions of it.

Are there other options? Could the Tag: header be marked as something
where package control files have priority over the overrides?


Ciao,

Enrico

Proposal for new debtags facet: "system"

Enrico Zini — 2012-01-21T14:55:57

Hello,

after some brainstorming with Thomas Goirand on IRC[2] about where to
place a "cloud" tag, the idea came out for a "system::*" facet as a spin
off of the "hardware::*" one, to represent the specific class of systems
a package can be specific for.

The idea is to take tags hardware::embedded and hardware::laptop out of the
hardware facet, leaving hardware more clearly defined as "peripherals", oo
"things with chips that you stick on a system", and add an orthogonal facet to
represent what kind of system a package would be specific for.

Here is a draft of the proposed new facet:

  Facet: system
  Description: Class of system
   Class of system a package provides specific functionality for.[1]

  Tag: system::cloud
  Description: Cloud
   Cloud computing is the delivery of computing as a service rather than
   a product, whereby shared resources, software, and information are
   provided to computers and other devices as a metered service over a
   network (typically the Internet).
   .
   Link: http://en.wikipedia.org/wiki/Cloud_computing

  Tag: system::embedded
  Description: Embedded
   A computer system designed for specific control functions within a larger
   system.
   .
   Link: http://en.wikipedia.org/wiki/Embedded_system

  Tag: system::laptop
  Description: Laptop
   A personal computer for mobile use.
   .
   Link: http://en.wikipedia.org/wiki/Laptop

  Tag: system::server
  Description: Server
   A physical computer (a computer hardware system) dedicated to
   running one or more such services (as a host),[1] to serve the needs
   of users of the other computers on the network. Depending on the
   computing service that it offers it could be a database server, file
   server, mail server, print server, web server, or other.
   .
   Link: http://en.wikipedia.org/wiki/Server_(computing)

  Tag: system::smartphone
  Description: Smartphone
   High-end mobile phone built on a mobile computing platform.
   .
   Link: http://en.wikipedia.org/wiki/Smartphone

  Tag: system::tablet
  Description: Tablet
   A mobile computer, larger than a mobile phone or personal digital assistant,
   integrated into a flat touch screen and primarily operated by touching the
   screen rather than using a physical keyboard
   .
   Link: http://en.wikipedia.org/wiki/Tablet_computer


I believe such a facet has *lots* of potential, and I am rather excited
about it.

Some notes up for discussion:

 - We could argue about where hardware::emulation belongs. I'd leave it
   in hardware because an emulated machine looks more like a virtual
   peripheral to me, rather than something that runs specific
   application. In a way, we could say that hardware::* is for software
   that works WITH that hardware, while system::* is for software that
   works IN that hardware.

 - Smartphones and tablets are becoming less and less like two different
   classes of systems: with tablets having GSM modems and smartphones
   working like tablets, one could say that a tablet is a smartphone
   that doesn't fit in a pocket. That means that most software that's
   typical of one platform will also be typical of the other one, and
   in fact apps are now developed targeting both systems as one.

   So they could very well be a single tag; the only problem is: how do
   we name it? Is there a better name than system::smartphone-tablet?

I'd give it a week worth of discussion, after which I'll try to wrap it
up and make it happen.



[1] This description in a better kind of English written needs to be.
[2] So you could know how we got to this proposal, here is the IRC
    conversation (I cut away the various digressions and other channel
    conversation, I hope I didn't cut anything relevant)

 enrico> zigo: I need to reread your mail to see if I catch the
 difference with admin::virtualisation; it's either I add that,
 or I propose a "buzzword" sort of facet with tags for all those
 names that people recognise
 zigo> Cloud computing *is not a buzz word*.
 zigo> jwilk: In short, management of a pool of servers for providing
       virtualmachines and storage.
 zigo> Only people who don't understand what it is think it's a buzz
       word.
 zigo> We wouldn't have about 100 binary packages in Debian *only* for
       doing cloud computing if it was just a buzz word.
 zigo> enrico: If you want to know why admin::virtualization isn't good
       for cloud, just think about server storage like Swift.
 enrico> zigo: right, so the idea would be to restrict
 admin::virtualisation to one-machine virtualisation
 infrastructure, and have admin::cloud to refer to
 migration/cloning/ui frontend/api interfaces?
 zigo> It doesn't do virtualization, has little do do with it, but it's
       managing potentially 100s of servers.
 enrico> uhm, ok, so things like openstack can also turn blades or
         servers on and off?
 zigo> Yup.
 zigo> Even physical machines.
 zigo> Like, for saving on power.
 enrico> ack
 zigo> There's also cloud without virtualization.
 zigo> Like, through an API, you'd get a new physical server.
 zigo> Get your OS installed automatically, and have your application to
       run on it.
 zigo> And possibly, do that with 10 servers at a time.
 enrico> so now another question is: is the level of abstraction of
 "cloud" one that fits in the "admin" facet? It sounds a bit
 more high levle than "configuring" "boot", "backup", "login"...
 enrico> how about a "solution::*" facet
 zigo> Basically, these are administration tools.
 zigo> So that you can remote-control servers.
 zigo> So yes, Admin:: would fit, IMO.
 enrico> zigo: uhm ok. So the tools themselves are as administration as
 'admin::login', only the system they manage is at a different
 abstraction level than, say, a single server. And that'd be
 fine indeed.
 zigo> Right.
 zigo> For example, quantum is a tool that manages VLANs for your cloud.
 zigo> So that each "customer" has the illusion that he's on its own
       VLAN, and wont see other private LANs.
 zigo> Using VLAN tagging on switches, and configuring openvswitch.
 zigo> That kind of things ...
 zigo> So that's really admin::
 enrico> zigo: otoh (still pondering) it's also ortogonal: you could do
 accounting, automation, backup, and son on, but "for cloud
 systems"
 enrico> zigo: so it could be, for example, hardware::cloud
 enrico> zigo: that way I can say admin::power-management &&
         hardware::cloud
 zigo> The issue I have with hardware:: is that it looks like it's full
       of drivers.
 zigo> Am I wrong?
 enrico> zigo: there's hardware::embedded, for example, which has
         embedded UI tools like GPE
 zigo> Like, I've put Swift (cloud object storage) to use
       hardware::storage, but it's confusing.
 zigo> It's a tool that uses rsync to have a level of redundancy.
 zigo> It doesn't act *at all* as a driver.
 zigo> People looking at for example iSCSI tools will find swift, and
       that's not what we want.
 zigo> You know better than me though.
 zigo> Maybe that would fit.
 enrico> zigo: right.
 http://debtags.debian.net/edit/tags/hardware::embedded is
 somewhat close, in that it says "this software is used in this
 specific class of hardware". Please ignore touchscreen drivers
 in that page: they are mistagged
 zigo> Ok.
 enrico> zigo: but if we think of tags to describe a "class of system",
 then cloud, server, embedded, tablet, smartphone could sound
 like points along the same axis
 enrico> (and they could be factored out of 'hardware' into a 'system'
         facet, at some point)
 enrico> zigo: I'm going for lunch, then I'll reply to your mail in
 debtags-devel along the lines of thinking of a 'system' facet
 zigo> enrico: I like the "class of system" concept.
 zigo> I really do.
 enrico> zigo: then we see what people say
 zigo> It'd be great to have a phone tag ...
 enrico> zigo: indeed. It's a tricky conceptual game, designing
         ontologies, isn't it? :)
 zigo> It is.


Ciao,

Enrico

Add new tag uitoolkit::xcb and maybe x11::composite-manager?

Arnaud Fontaine — 2012-01-17T02:45:51

Hello,

Could it be possible to add a  new tag uitoolkit::xcb? ATM there is only
uitoolkit::xlib but many packages are using xcb instead of xlib.

Also, even though it would only concern very few packages, I'm wondering
if a  tag x11::compositing-manager  or x11::composite-manager  should be
added?

Regards,

hardware:: tag matching lib plans

Michael Vogt — 2012-01-16T08:30:41

Hi,

for the software-center I'm currently looking into building a lib that
can match a debtag hardware:: tag (like hardware::storage:dvd) to the
capabilities of the actual computer. This will allow us to show
information in the GUI like: "This software requires a touchscreen,
but the computer does not have one." [2]

For this I would like to talk about some new tags that look useful in
this context:

Tag: hardware::input:touchscreen
Description: Requires a touchscreen input

Tag: hardware::storage:cd:writer
Description: Compact Disc writer
(or hardware::storage:cd-writer ?)

Tag: hardware::storage:dvd:writer
Description: Digital Versatile Disc writer



Here are two more that are a little more difficult. The tag would
embed a number that the lib parses then. I'm not sure how well that
fits into the general schema of debtags. If its does not fit I wonder
if it could be done as a private extension to the system? Would we
prefix it in some special way?

Tag: hardware::memory:{1,2,4,8}GB
Description: Requires at least N amount of RAM 

Tag: hardware::video:opengl:{2,3,4.1,4.2}
Description: Requires at least N opengl level to run


Thanks and looking forward to your feedback,
 Michael


[1] https://code.launchpad.net/~mvo/software-center/python-halali
[2] https://wiki.ubuntu.com/SoftwareCenter#Hardware_requirements

More tags for scope::* ?

Enrico Zini — 2012-01-15T10:59:41

[reposted to debian-devel because the issue is tricky and more people
 hopefully mean more clues]

Hello,

Let's look at the uses of the scope facet:
http://debtags.debian.net/reports/facets/scope

It would be nice if we could say "if a package has role::program, then
it should also have some scope::* tag". However, the current contents of
the scope facet are probably not enough to cover all programs in Debian:

   http://debtags.debian.net/search/bytag?wl=role::program&bl=scope::application,scope::utility
   http://debtags.debian.net/edit/tags/role::program,-scope::application,-scope::utility

Those reports show(especially the second link that is sorted by
popularity) quite a bit of programs that are neither apps nor utilities:

 - essential system management: login, apt, bsdmainutils, passwd, udev,
   dbus, consolekit, nfs-common, rsyslog, portmap, acpid, ...
 - system services: openssh-server, exim4-daemon-light, ...
 - compilers and interpreters: perl, python2.6, ...

"scope::infrastructure" is a new tag that would come to mind, although
I'm not sure it would really cut it for compilers and interpreters, when
seen as development tools, although in a way they are.

Ideas?


Ciao,

Enrico

More tags for scope::* ?

Enrico Zini — 2012-01-14T13:24:09

Hello,

Let's look at the uses of the scope facet:
http://debtags.debian.net/reports/facinfo/scope

I was considering adding a hint in the form "if it has role::program
then it should also have some scope::* tag", but before doing so I was
running a reality check on those packages that at the moment have
role::program but no scope::* tags:

   http://debtags.debian.net/search/bytag?wl=role::program&bl=scope::application,scope::utility
   http://debtags.debian.net/edit/tags/role::program,-scope::application,-scope::utility

That shows (especially the second link that is sorted by popularity)
quite a bit of programs that are neither apps nor utilities:

 - essential system management: login, apt, bsdmainutils, passwd, udev,
   dbus, consolekit, nfs-common, rsyslog, portmap, acpid, ...
 - system services: openssh-server, exim4-daemon-light, ...
 - compilers and interpreters: perl, python2.6, ...

"scope::infrastructure" is a proposal that would come to mind, although
I'm not sure it would really cut it for compilers and interpreters, when
seen as development tools, although in a way they are.

Comments?


Ciao,

Enrico

New tag suite::postgresql

Christoph Berg — 2012-01-12T10:33:02

Hi,

there quite an amount of postgresql-related packages in Debian:

http://qa.debian.org/developer.php?login=pkg-postgresql-public%40lists.alioth.debian.org
lists 48 source packages - probably even more that I haven't spotted yet.

I'd propose a new tag suite::postgresql to mark them.

Thanks for considering,
Christoph

A small big step towards a new webapp

Enrico Zini — 2011-12-23T15:52:47

Hello,

you may not notice it (in fact, if all goes well you MUST NOT notice it
:P) but http://debtags.alioth.debian.org/todo.html and
http://debtags.alioth.debian.org/edit.html are now powered by the new
django-based backend code running at debtags.debian.net on DSA-managed
machines.

That is the new site coming to life. Besides a legacy API-compatible
interface which can power the old webapps, there are some prototype
report pages:

  http://debtags.debian.net/rep/todo/
  http://debtags.debian.net/rep/todo/maint/enrico< at >debian.org

Note that it now knows of source packages, so it can group binary
packages by sources in a maintainer view.

The code is here:

  http://anonscm.debian.org/gitweb/?p=debtags/debtagsd.git;a=summary

And now it is finally humanly possible to add new features to the
website.

There are a few things that I still need to work on before the migration
is functionally complete:

 - daily backup of the tag database: broken since today
 - automatic tagging of not-yet-tagged packages: broken since today
 - statistical generation of tag suggestions: broken since today
 - daily update of vocabulary browser: broken since today
 - email patch submission: broken since April Alioth migration
 - QA tags generation: broken since April Alioth migration
 - aggregate patches by submitter for approval: broken since Alioth
   migration

Other experimental pages (tag cloud, smart search) have been broken
since I don't know how long, and they can now, finally, be properly
reimplemented on a proper webapp.


Ciao,

Enrico

"works-with::unicode" tag and "rxvt-unicode" package

Matej Kosik — 2011-09-28T09:33:59

Hello,

I would like to ask, whether it makes sense to keep the "works-with::unicode" tag for "rxvt-unicode" package?

Is there somewhere a document that describes semantics of individual tags?
--
Matej Kosik

Debtags at debcamp

Enrico Zini — 2011-07-14T19:10:14

Hello,

I'll be at Debcamp from the 19th. Will there be others interested in
Debtags?


Ciao,

Enrico

Applying debtags to new basex package

Alexander Holupirek — 2011-05-20T12:33:52

Hi,

I wanted to ask what's the recommended way to apply debtags to a new
package?
When I browse to [1] and follow the Debtags link (as supposed by
[2]) I see now way to add those tags in [3].

Probably I am missing something?

The package I want to tag is basex [4].

Thanks in advance,
Alex

[1] http://qa.debian.org/developer.php?login=alex< at >holupirek.de&comaint=yes
[2] http://debtags.alioth.debian.org/faq.html#how-can-maintainers-interact-with-debtags
[3] http://debtags.alioth.debian.org/todo.html?maint=alex%40holupirek.de
[4] http://packages.debian.org/en/sid/basex

need to reuse a debtag page

Raul Perez-Alejo Neyra — 2011-04-07T19:36:05

  Hello, i was implementing something similar to

http://debtags.alioth.debian.org/cloud/
and
http://debtags.alioth.debian.org/fts.html

for the same propouse, but i was wondering if there is any posible way 
to reuse this same pages. Are they package?, if not, is there any way to 
package them?

hugs,

proposing a new debtag for "ical"

Stefano Zacchiroli — 2011-04-03T16:53:50

Hi Andrew,
  discussing with Enrico, we noticed that there is at present no
works-with-format::ical debtag, to identify all apps able to process
ical files. The standard procedure to propose a suitable new tag is at
http://debtags.alioth.debian.org/faq.html#what-makes-a-tag-good-for-being-added-to-the-vocabulary
but the problem is that neither I nor Enrico know much about calendar
formats.

So, if you don't mind, we're coming to you for help with a few
questions:

- would "ical" be an appropriate name for such a format or should it
  rather be something else?

- if we go ahead and add "ical", should be also add some other related
  formats?

- do you have an initial list of packages to suggest that could form an
  initial set of debtagged packages for the debtags we are going to
  introduce?

Many thanks in advance!
Cheers.

my own tags

Raul Perez-Alejo Neyra — 2011-03-21T20:22:26

  Hello community, i found this idea of Debtags, and i think is 
wonderfull, so i came up with some implementation troubles:

1- i did my own Vocabulary, that response to my organizations needs. 
When i use "debtags" command to see tags, everything goes right, but 
when i use "packagekit" i can't see my tags, and GUI are important for 
non-command line users.

2- I would like to have also something like 
"http://debtags.alioth.debian.org/cloud/" inside my organizations, so i 
could mix repository pkg with mine. Is it package??? so y can download 
it and use it ?????

Hugs,

New tags proposals

Pino Toscano — 2011-03-20T14:22:00

Hi,

I have been debtagging packages since a couple of years or so, using the 
web interface, and collecting proposals for what I think they could be 
new tags.
(PS: I'm not subscribed, so please CC me on replies)

tag: culture::galician
description: Galician
packages:
  kde-l10n-gl
  kdevelop-l10n-gl
  kdevelop-php-docs-l10n-gl
  kdevelop-php-l10n-gl
  kdevplatform-l10n-gl
  koffice-l10n-gl
  hunspell-gl-es
  icedove-l10n-gl
  iceweasel-l10n-gl
  libreoffice-help-gl
  libreoffice-l10n-gl

tag: culture::lithuanian
description: Lithuanian
packages:
  kde-l10n-lt
  link-grammar-dictionaries-lt
  myspell-lt
  icedove-l10n-lt
  iceweasel-l10n-lt
  libreoffice-l10n-lt

tag: protocol::gopher
description: Gopher
packages:
  kio-gopher
  libwww-perl
  gopher
  forg
  php5-curl
  pavuk
  pygopherd

tag: web::microblog
description: Microblog software
packages:
  choqok
  gwibber
  libmicroblog4
  identicurse
  qwit
  ttytter
  pino
  smuxi-engine-twitter
  twidge
  (and more)

tag: works-with-format::chm
description: Compiled HTML Help
  http://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help
packages:
  libchm1
  python-chm
  okular-backends-extra
  kchmviewer
  xchm
  fbreader
  chmsee
  archmage
  chm2pdf
  calibre-bin

Plus there are a couple of tags which would not reach 6 users, but IMHO 
they would be worth to be added:

tag: culture::indonesian
description: Indonesian
packages:
  kde-l10n-id
  gcompris-sound-id
  icedove-l10n-id
  iceweasel-l10n-id
  libreoffice-l10n-id

tag: works-with-format::epub
description: EPub electronic publication
  http://en.wikipedia.org/wiki/EPUB
packages:
  libepub0
  calibre
  dbtoepub
  fbreader
  okular-backends-extra

Thanks for debtags,