Support StarDict format! #21
Comments
|
Download http://sourceforge.net/projects/stardict-4/files/3.0.6/stardict-3.0.6.tar.bz2/download Look at tools/tabfile.cpp ! |
|
It seems to me that it should be the opposite, that StarDict should support a standard format but.... |
|
Hi
Quentin Nerden
It seems to me that it should be the opposite, that StarDict should support a standard format but....
There's no standard format :). XDXF tried to establish something alike, but it
was "yet another format". TEI is great because it allows to express almost all
we could ask for, but it's less useful for "displaying" dictionaries to a user.
In my opinion, we should focus on the most popular formats and that is today
Slob and StarDict to some extend.
I already wrote about my concerns about StarDict though.
|
|
I'm not sure what you mean, Sebastian, when you say that the TEI "is less useful for "displaying" dictionaries to a user" -- it's as useful as any XML, and then some more, given that it has seen a lot of applications and therefore some ready-made display solutions exist. We've just never cared much about displaying TEI dictionaries as such, because TEI was treated as a storage format for conversion into (initially) DICT and other formats. For TEI, I once whipped up some sketchy CSS, just to demonstrate to students at some seminars that it can easily be done. Perhaps we should revisit the issue of displaying the source TEI in the browser? As for the initial message in this thread -- I think we used to have some export to StarDict or its predecessor, but it may have vanished in the recesses of the past. The idea is just as plausible as having export to DICT (maybe even more plausible nowadays). But, frankly, I would expect a minimal gesture on the part of the StarDict developer of providing us with a spec of the format, rather than sending us on an Easter egg hunt somewhere... :-) |
|
I'm not sure what you mean, Sebastian, when you say that the TEI "is less
useful for "displaying" dictionaries to a user" -- it's as useful as any XML,
and then some more, given that it has seen a lot of applications and therefore
some ready-made display solutions exist.
One of the jpn-* dictionaries is above 100M in size. It is comprehensive, yet
not complex. Loading it even in Vim takes long, I'd argue that using it with a
CSS style sheet in a browser would not be necessarily a good user experience.
Apart from it, TEI has not been designed to allow fast indexing, StarDict (and
the predecessor "dict") care about such details. Viewing a dictionary is nice,
searching the contents is much more important. Maybe I'm overlooking something?
Perhaps we should revisit the issue of displaying the source TEI in the browser?
For my part, I'm not interested in this.
As for the initial message in this thread -- I think we used to have some
export to StarDict or its predecessor, but it may have vanished in the recesses
of the past. The idea is just as plausible as having export to DICT (maybe even
more plausible nowadays).
Who is the StarDict author these days? There is starDict and StarDict-4 and
there is a GitHub mirror. I am not sure whom to contact.
|
I'd say you've seen clearly through my unclear post. I went from a point I wished to make (that XML in general, and TEI in particular, is not a hindrance to visualisation) to mentioning CSS as if it were a solution (and you then correctly pointed out the size of some databases).
Again, my bad, because in the context, this can readily mean "by using CSS", and that is clearly only workable for small databases, and even then non-optimal (XSLT in the browser would probably be slightly better, because it would at least let you copy everything, unlike CSS). So let me restate: Perhaps we should look at ways to visualise the source TEI without pre-conversion into text-based formats? A possible path could be to base our TEI off the so-called TEI Lex0, which is a format intended as pivot for "retrodigitized" dictionaries that is being currently pushed onto a standardization track, and then see what TEI Lex0 enabled tools can be used for the display? Conversion of Freedict TEI towards a TEI Lex0 version should not be overly complex -- I think most stuff would remain as is, with some tweaks in attribute values and such. But, naturally, it would be good to wait until Lex0 gets frozen, so it's not a project for right now.
My understanding was that the author is the original poster in this thread. |
|
http://stardict-4.sourceforge.net/StarDictFileFormat
Piotr Banski <[email protected]> 于2019年6月10日周一 下午8:41写道：
… @piotr <https://github.com/piotr>
I'm not sure what you mean, Sebastian, when you say that the TEI "is less
useful for "displaying" dictionaries to a user" -- it's as useful as any
XML, and then some more, given that it has seen a lot of applications and
therefore some ready-made display solutions exist.
One of the jpn-* dictionaries is above 100M in size. It is comprehensive,
yet not complex. Loading it even in Vim takes long, I'd argue that using it
with a CSS style sheet in a browser would not be necessarily a good user
experience. Apart from it, TEI has not been designed to allow fast
indexing, StarDict (and the predecessor "dict") care about such details.
Viewing a dictionary is nice, searching the contents is much more
important. Maybe I'm overlooking something?
I'd say you've seen clearly through my unclear post. I went from a point I
wished to make (that XML in general, and TEI in particular, is not a
hindrance to visualisation) to mentioning CSS as if it were a solution (and
you then correctly pointed out the size of some databases).
Perhaps we should revisit the issue of displaying the source TEI in the
browser?
For my part, I'm not interested in this.
Again, my bad, because in the context, this can readily mean "by using
CSS", and that is clearly only workable for small databases, and even then
non-optimal (XSLT in the browser would probably be slightly better, because
it would at least let you copy everything, unlike CSS). So let me restate:
Perhaps we should look at ways to visualise the source TEI without
pre-conversion into text-based formats?
A possible path could be to base our TEI off the so-called TEI Lex0, which
is a format intended as pivot for "retrodigitized" dictionaries that is
being currently pushed onto a standardization track, and then see what TEI
Lex0 enabled tools can be used for the display?
Conversion of Freedict TEI towards a TEI Lex0 version should not be overly
complex -- I think most stuff would remain as is, with some tweaks in
attribute values and such. But, naturally, it would be good to wait until
Lex0 gets frozen, so it's not a project for right now.
As for the initial message in this thread -- I think we used to have some
export to StarDict or its predecessor, but it may have vanished in the
recesses of the past. The idea is just as plausible as having export to
DICT (maybe even more plausible nowadays).
Who is the StarDict author these days? There is starDict and StarDict-4
and there is a GitHub mirror. I am not sure whom to contact.
My understanding was that the author is the original poster in this thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21?email_source=notifications&email_token=ABFJJI6OFQXELQW5X7ZKNPDPZZDWXA5CNFSM4G2MZFH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJYPLY#issuecomment-500402095>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFJJI7DOOG2LQAOB4LZRY3PZZDWXANCNFSM4G2MZFHQ>
.
|
|
So I tagged this as help wanted because we currently lack manpower to implement this. @huzheng001 Can you look into this? |
|
You can use PyGlossary to convert FreeDict(tei) or slob files to StarDict. |
|
Yes, we are investigating this and @karlb is AFAIK working on Pyglossary to
some extend. Can you please provide us with recent applications that make use
of the StarDict format? Are there any mobile applications?
|
|
Yes, for Android there is GoldenDict Free which contains ads. |
|
For desktop there is GoldenDict and StarDict. |
|
There is also sdcv which a simple command line application (for Linux / Unix, works on Android Termux too). |
|
Use PyGlossary is OK!
Saeed Rasooli ***@***.***> 于2020年9月3日周四 03:23写道：
… There is also sdcv <https://github.com/Dushistov/sdcv> which a simple
(non-interactive) command line application (for Linux / Unix, works on
Android Termux too)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFJJI5MZBDCYNUZ3IFXUT3SD2LUBANCNFSM4G2MZFHQ>
.
|
|
Would you be willing to help us integrate it into our build system?
|
Sure. |
|
Hi
Where are your build config files?
Please see the overview at
<https://github-wiki-see.page/m/freedict/fd-dictionaries/wiki/FreeDict-HOWTO-%E2%80%93-FreeDict-Build-System>.
The relevant files are in mk/, while you probably only need to care about
dicts.mk.
Thanks
|
|
Looks like you convert tei to dictd ( I think we need to convert |
|
No, whatever is in the Makefile that talks about StarDict is outdated. I would
suggest that you read how the conversion to dictd works and just mimic the
same to imlement StarDict. The ol StarDict rules should be removed.
|
|
Pyglossary can already be used to convert the TEI files generated by WikDict (many of which are part of FreeDict) to arbitrary formats. I've used it to create StarDict and Kobo dictionaries for the last years. But I'm not sure how well it copes with the other TEI files. I personally find dealing with pyglossary a lot easier (both executing it and changing its code) than with the XLST files, so if there is an easy way to go directly from all our TEI files to pyglossary's different output formats, I would be in favor of doing that. |
|
I would restrict the scope of the issue to StarDict. If we could get this
working and integrated into the build system, as we integrated e.g. tei2slob,
we can then evaluate about switching to Pyglossary for everything. But as a
first step, I would like to see how well it copes the the variety of
dictionary encodings that we have.
|
|
Hi, I noticed that the StarDict files downloadable on the FreeDict website don't have (I'm not completely sure this is the correct repository to report this to, if there is a better one, please do tell.) |
|
Thanks, that is likely an oversight, I'll check it but cannot promise to do it
in the next days. IMO the stardict files are not yet advertised on the
download page, are they?
|
|
Thanks for the reply, as long as doesn't get forgotten and gets fixed eventually, sounds good.
I believe I searched for Stardict dictionaries and the FreeDict website was returned. It doesn't mention StarDict per se, but it does mention GoldenDict and |
|
Ah wait. These files are for the **dict** client. We just recently gained
support for **stardict**, just don't offer the files yet on the website. Please
head over to https://download.freedict.org/dictionaries/ and pick the atest
release of your desired dictionary. Except for eng-pol, it should have a
stardict archive. Please download and test.
|
|
Ah, I see, sorry for the confusion. I can see the |
|
https://stardict-4.sourceforge.net/pan_baidu_code.html
sdasda7777 ***@***.***> 于2024年1月20日周六 00:06写道：
… Ah, I see, sorry for the confusion. I can see the .ifo file being
present, and it does work on my reader!
—
Reply to this email directly, view it on GitHub
<#21 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFJJI4CSPN6Y5BT57JBTATYPKKYDAVCNFSM4G2MZFH2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJQGA3DQOJYGMZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Could you make every dictionary here have a StarDict format version?
Then in http://download.huzheng.org I can create a link to your freedict sourceforge project!
The text was updated successfully, but these errors were encountered: