Skip to content
This repository has been archived by the owner on Aug 18, 2018. It is now read-only.

support sametypesequence for stardict #14

Open
aw-bib opened this issue Nov 9, 2015 · 3 comments
Open

support sametypesequence for stardict #14

aw-bib opened this issue Nov 9, 2015 · 3 comments

Comments

@aw-bib
Copy link

aw-bib commented Nov 9, 2015

The sametypesequence stanza in the ifo file defines, which syntax is used in the definition block. Currently, penelope seems to allow only for m, which treats whatever as plain text. The following types are known to stardict

  • 'm' Word's pure text meaning. The data should be a utf-8 string ending with '\0'.
  • 'g' A utf-8 string which is marked up with the Pango text markup language.
  • 't' English phonetic string. The data should be a utf-8 string ending with '\0'.
  • 'x' A utf-8 string which is marked up with the xdxf language.
  • 'y' Chinese YinBiao or Japanese KANA. The data should be a utf-8 string ending with '\0'.
  • 'k' KingSoft PowerWord's data. The data is a utf-8 string ending with '\0'.
  • 'w' MediaWiki markup language.
  • 'h' Html codes.
  • 'n' WordNet data.
  • 'r' Resource file list.
  • 'X' this type identifier is reserved for experimental extensions.

cf. StarDict on Google Code for details.

@pettarin
Copy link
Owner

Unfortunately, I no longer have time to develop or maintain Penelope: https://github.com/pettarin/penelope#important-updates

@pettarin
Copy link
Owner

Added the text-like, UTF-8 encoded formats in v3.0.0: https://github.com/pettarin/penelope/blob/master/penelope/format_stardict.py#L32

The contents are not parsed, though.

@pettarin
Copy link
Owner

pettarin commented Mar 4, 2018

In view of https://github.com/pettarin/penelope#important-update I leave the issue open, but I do not plan to address it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants