Mailinglist Archive: opensuse-translation (5 mails)

< Previous Next >
Re: [opensuse-translation] Dictionaries - usage, upstream, updates
  • From: Vojtěch Zeisek <vojtech.zeisek@xxxxxxxxxxxx>
  • Date: Tue, 29 Oct 2019 13:28:10 +0100
  • Message-id: <2018394.tJJNFtfspm@tilia>
Hi,
sorry for long silence, my mail system just quietly dropped this mail as spam
(I had to download it from the archive)... :-/ I'll try to resurrect some
questions below...

Dne úterý 8. října 2019 9:51:29 CET, Tomas Chvatal napsal(a):
Vojtěch Zeisek píše v Út 08. 10. 2019 v 09:31 +0200:
Hi,
there is recent work on new Czech dictionary, which should
have better vocabulary and should be better in handling complex
Czech grammar. The work is still far from being complete, but
so far it's promising. Some info (mostly in Czech, sorry) is at
https://gitlab.com/strepon/czech-cc0-dictionaries/ and
http://ceskeslovniky.cz/about.html and https://github.com/l10ncz/
We discussed this at https://www.linuxdays.cz/2019/en/ last
weekend (BTW, (open)SUSE had the best presentation there) and
there were couple of questions we were unable to answer, so I
seek advice here. :-)
The dictionary above is now available as hunspell addon for LO.
This format is used also by FF, TB and more. But what about KDE,
GNOME, other DEs, Qt (non-KDE) apps? Others? What do they use?

I'm sorry, I could be looking wrongly, I didn't find which dictionaries are
used by all the desktop environments and another big projects... Any idea?

In another words, what is purpose of having distribution packages
for aspell, ispell, hunspell, myspell? What is relationship among
them? What is used for what?

I still wonder what is used for what...

Regarding hunspell/myspell, what is upstream for the dictionaries?

So the upstream is LO. Is it so for all projects/distributions?

We were unable to find where does the Czech dictionary came from. :-)
One day we'd like to merge the new dictionary with the existing
one, but it requires much more work now. Anyway, it'd be good to
have distribution package available for testing. We then wonder
if it's possible to have installed together e.g. myspell-cs_CZ
and myspell-cs_CZ_EXPERIMENTAL and somehow switch between them.
Or more general, how is packaging of dictionaries organized?
Technically as well as getting the data.
I'm looking forward for any point on this topic.
V.

Hello Vojtech,
I so wanted to join this chat, but sadly as and Org didn't get
the time to do much else except handling the conference itself.
The first thing I have is that we set up the dictionaries to be
auto-generated from the libreoffice-dictionaries repository for
all the languages.

Do You mean all hunspell dictionaries, or also myspell and I don't know what
else? So for openSUSE, is LO the upstream? Do You know if it's general
upstream for everyone using hunspell?

The previous approach was individual projects and packages and
it was pain in the butt to keep it up-to-date and working well.

I can imagine, I wonder how this is organized, also in other distributions.

So I would first recommend to take that project and integrate
them in LO [1] and we will automatically inherit them.

According to Stanislav Horáček maintaining the new project, it's not ready
yet...

For the interim testing you can name the package as i.e. 'hunspell
-new-cs_CZ' and have it provide the symbols of the other czech
dictionary name and at the same time conflict with it. It will
let users choose the dictionary.

Do You mean usage of update-alternatives according to <https://
en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines> ?

But I can't stress enough how much pain it was to keep the
separate pkgs for various languages so really try to integrate
it in the libreoffice.

It'd planned, but it seems there is still plenty of work to be done, so it
won't be soon...

Cheers
Tom
[1] https://cgit.freedesktop.org/libreoffice/dictionaries/

Kind regards,
V.

--
Vojtěch Zeisek

Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux

https://www.opensuse.org/
https://trapa.cz/
< Previous Next >
List Navigation
Follow Ups