Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Quoting Pander (2018-07-07 13:15:26) > Thanks, but that was not the assumption, rather the assumption that > myspell-xx and hunspell-xx are offering the same content. And Hunspell > succeeded MySpell. Based on that, that the hunspell package is the > newer or more up to date. Hunspell _format_ succeeded Myspell, but _dictionaries_ exist using either format. It is wrong to assume that an american english disctionary is more up to date than a british english dictionary, based on the lingual _regions_ being of different age. > The situation now is, that there is "myspell-xx-author1" and > "hunspell-xx-authorA". Similar case would be that "python-numpy" and > "python3-numpy" are assumed to be by the same author and offer the > same functionality. The comparable situation is if one upstream project provides numpy only for Python 3.x, and another(!) upstream project provides numby only for Python 2.x. that is technically possible, but less likely than for one dictionary to be offered in myspell format and another offered in hunspell format. > A mistake that could be made less often with perhaps other package > names (-dsdo), especially by non-advanced users. But I leave it at > what it is, wontfix. Thanks for your feedback. It would indeed make good sense for the packages to be distinguishable by suffix, when originating from different upstream sources. What would make more sense to me, however, is that the newer dictionary from different upstream source (and with weaker coverage) was renamed, rather than the older well-established one. If you agree, then please reasign to hunspell-da. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Thanks, but that was not the assumption, rather the assumption that myspell-xx and hunspell-xx are offering the same content. And Hunspell succeeded MySpell. Based on that, that the hunspell package is the newer or more up to date. The situation now is, that there is "myspell-xx-author1" and "hunspell-xx-authorA". Similar case would be that "python-numpy" and "python3-numpy" are assumed to be by the same author and offer the same functionality. A mistake that could be made less often with perhaps other package names (-dsdo), especially by non-advanced users. But I leave it at what it is, wontfix. Thanks for your feedback. On 07/07/2018 12:45 PM, Jonas Smedegaard wrote: > Quoting Pander (2018-07-07 12:00:02) >> Thanks for the explanation. That doesn't make it easier for the end >> user. Me and my colleagues also thought that hunspell-da is _the_ one >> and best one to use and that myspell-da is the same, but created a >> while back and packaged for myspell. Easy mistake to make. > Please clarify what is the issue, before trying to solve it. > > It seems you make an assumption that there will be one true correct > disctionary for each language. I disagree with that. > > how do you know if "Oxford English Dictionary" is the one you want for > english? > > > - Jonas >
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Quoting Pander (2018-07-07 12:00:02) > Thanks for the explanation. That doesn't make it easier for the end > user. Me and my colleagues also thought that hunspell-da is _the_ one > and best one to use and that myspell-da is the same, but created a > while back and packaged for myspell. Easy mistake to make. Please clarify what is the issue, before trying to solve it. It seems you make an assumption that there will be one true correct disctionary for each language. I disagree with that. how do you know if "Oxford English Dictionary" is the one you want for english? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Thanks for the explanation. That doesn't make it easier for the end user. Me and my colleagues also thought that hunspell-da is _the_ one and best one to use and that myspell-da is the same, but created a while back and packaged for myspell. Easy mistake to make. How are these differentiated for e.g. LibreOffice? I have no idea how to improve this, perhaps: - hunspell-da (non-DSDO, leave as is) - myspell-da (DSDO) move content to hunspell-da-dsdo and convert myspell-da into a dummy transitional package depending on hunspell-da-dsdo Something like this would put the arguably superior Danish spelling support in a better position, package name-wise. Leveling the playing field. Additionally, LibreOffice could also ship it as da-dsdo. Currently, only the arguably less-superioir Danish support is in there, see https://cgit.freedesktop.org/libreoffice/dictionaries/tree/ But it is just an idea and leave it up to you. On 07/04/2018 02:37 PM, Agustin Martin wrote: > Control: tags -1 +wontfix > > On Tue, Jul 03, 2018 at 07:48:58PM +0200, Jonas Smedegaard wrote: >> hunspell-da and myspell-da is indeed different dictionaries. >> >> They cannot be merged due to different licensing: The oldest and most >> comprehensive project (DSDO) chose a strong copyleft license, and the >> newer project (Stavekontrolden) started from scratch to be able to >> choose a different license. >> >> myspell-da is _not_ obsolete - it is arguably superior to hunspell-da >> despite its older - but compatible - container format. > Thanks for the info, Jonas. > > Tagging as wontfix. >
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Control: tags -1 +wontfix On Tue, Jul 03, 2018 at 07:48:58PM +0200, Jonas Smedegaard wrote: > > hunspell-da and myspell-da is indeed different dictionaries. > > They cannot be merged due to different licensing: The oldest and most > comprehensive project (DSDO) chose a strong copyleft license, and the > newer project (Stavekontrolden) started from scratch to be able to > choose a different license. > > myspell-da is _not_ obsolete - it is arguably superior to hunspell-da > despite its older - but compatible - container format. Thanks for the info, Jonas. Tagging as wontfix. -- Agustin
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Quoting Agustin Martin (2018-07-03 18:31:16) > Control: severity -1 wishlist > > On Tue, May 15, 2018 at 01:52:32PM +0200, Pander wrote: > > Package: myspell-da > > Version: 1.6.36-9 > > Severity: normal > > Tags: l10n > > > > Convert myspell-bg into dummy transitional package depending on > > hunspell-da and gradually phase out myspell-da. Myspell is no longer > > shipped and most other packages have migrated to the Hunspell package > > names. For example, see also > > https://packages.debian.org/stretch/myspell-af and > > https://packages.debian.org/stretch/myspell-ca Note that the internal > > format of the files for Myspell and Hunspell is identical, so this > > concerns only the packaging. > In this particular case, lo-dicts ships hunspell-da, however from > different author > > hunspell-da: > Copyright (C) 2014 Foreningen for frit tilgængelige sprogværktøjer > Website: http://www.stavekontrolden.dk > E-mail: i...@stavekontrolden.dk > License: GPL 2.0/LGPL 2.1/MPL 1.1 tri-license > > myspell-da: > Copyright (C) 1998-2004 Skåne Sjælland Linux User Group > and the contributors. > License: GPL 2+ > Website: http://da.speling.org/fejlmelding/ > > In these cases, we usually select one of them only if there is a clear > consensus that one is clearly better than the other. Otherwise, I > personally prefer to keep both. > > Jonas, what the Danish users groups think about these two dicts? > > Considering current versions, if it is clear that hunspell-da should > supersede myspell-da, it is better if lo-dicts ships the transitional > myspell-da. Once it reaches testing we can remove old myspell-da and > the transition would be complete. > > Note that this requires agreement from myspell-da maintainer(s). hunspell-da and myspell-da is indeed different dictionaries. They cannot be merged due to different licensing: The oldest and most comprehensive project (DSDO) chose a strong copyleft license, and the newer project (Stavekontrolden) started from scratch to be able to choose a different license. myspell-da is _not_ obsolete - it is arguably superior to hunspell-da despite its older - but compatible - container format. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Control: severity -1 wishlist On Tue, May 15, 2018 at 01:52:32PM +0200, Pander wrote: > Package: myspell-da > Version: 1.6.36-9 > Severity: normal > Tags: l10n > > Convert myspell-bg into dummy transitional package depending on > hunspell-da and gradually phase out myspell-da. Myspell is no longer > shipped and most other packages have migrated to the Hunspell package > names. For example, see also > https://packages.debian.org/stretch/myspell-af and > https://packages.debian.org/stretch/myspell-ca Note that the internal > format of the files for Myspell and Hunspell is identical, so this > concerns only the packaging. Hi, In this particular case, lo-dicts ships hunspell-da, however from different author hunspell-da: Copyright (C) 2014 Foreningen for frit tilgængelige sprogværktøjer Website: http://www.stavekontrolden.dk E-mail: i...@stavekontrolden.dk License: GPL 2.0/LGPL 2.1/MPL 1.1 tri-license myspell-da: Copyright (C) 1998-2004 Skåne Sjælland Linux User Group and the contributors. License: GPL 2+ Website: http://da.speling.org/fejlmelding/ In these cases, we usually select one of them only if there is a clear consensus that one is clearly better than the other. Otherwise, I personally prefer to keep both. Jonas, what the Danish users groups think about these two dicts? Considering current versions, if it is clear that hunspell-da should supersede myspell-da, it is better if lo-dicts ships the transitional myspell-da. Once it reaches testing we can remove old myspell-da and the transition would be complete. Note that this requires agreement from myspell-da maintainer(s). Thanks for your contribution, -- Agustin
Bug#898711: myspell-da: Convert into dummy transitional package depending on hunspell-da
Package: myspell-da Version: 1.6.36-9 Severity: normal Tags: l10n Convert myspell-bg into dummy transitional package depending on hunspell-da and gradually phase out myspell-da. Myspell is no longer shipped and most other packages have migrated to the Hunspell package names. For example, see also https://packages.debian.org/stretch/myspell-af and https://packages.debian.org/stretch/myspell-ca Note that the internal format of the files for Myspell and Hunspell is identical, so this concerns only the packaging. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages myspell-da depends on: ii dictionaries-common 1.27.2 myspell-da recommends no packages. Versions of packages myspell-da suggests: pn mozilla-browser pn mozilla-mailnews pn mozilla-thunderbird pn openoffice.org -- no debconf information
