Lior,

On Tuesday, January 14, 2025 12:39:01 AM MST Lior Kaplan wrote:
> You're welcome to salvage these packages any way.
> Please don't remove any comment / feedback you have already made.
> 
> Manuel - Thanks for your contribution (and I hope we'll see more in the
> future).

If you have any willingness to continue to maintain the package I would be 
pleased if you did, especially if you have any ability to understand Arabic.  
I always think it is best if someone maintaining a dictionary has at least a 
little ability to understand the language of the dictionary, which I do not in 
this case.

Questions regarding the package that I think are best addressed by the 
maintainer:

1.  Should we prefer to do as much as possible to debian/* files as opposed to 
using debian/rules?  For example, should the cleaning of the ar.bdic package 
be handled in debian/clean or in debian/rules.  Either works, but some 
maintainers have a preference for one or the other.

2.  This package generates a large number of symlinks, for example, from 
ar_AE.aff to ar.aff.  Whenever a package ships different dictionaries for a 
regional variation of the language there should, of course, always exist 
separate files for that region.  In the case where there are no regional 
differences shipped, most Hunspell packages do not create symlinks for these 
regions.  Typically, if a user has selected a regional variation in the 
interface of whatever program they are using, it will automatically fall back 
to the general language file if the regional variation is not available.

So, the question is if you have a strong preference to maintain these links 
(perhaps there is a particular reason they are important in Arabic).  If so, 
should we also generate them for the .bdic file?  Note that even if they are of 
use for the main Hunspell dictionary files, they are less likely to be of use 
for .bdic.  This is because of the way they have to manually be enabled by 
programs using Qt WebEngine.  As an example, Privacy Browser, which I maintain 
(and am upstream), is programmed to not even display symlinked .bdic files in 
the list of options.

3.  This is mentioned in the MR, but we should probably add a `Files: *` 
stanza to debian/copyright, and we need to generate something for `Files: 
debian/*`.

-- 
Soren Stoutner
so...@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to