|
|
发表于 2016-8-5 19:33:24
|
显示全部楼层
本帖最后由 Slav 于 2016-8-5 20:39 编辑
r8 l" Q% ?- e$ U5 C; v w! _9 u* X! J& A9 _1 I# [6 J
Just started to dive into the regex expressions field since it is really a good idea to parse MDX source. Will check it out later on.
' O- y0 } ~6 U' Y( `/ g, f4 R& q* G* z9 j F6 \
The idea about creating MDX from TXT is following. The following thoughts are just my fantasy, but I believe it can be released in this software.
& f0 h8 x0 i0 U0 W1 C+ ~2 oYou define the structure of TXT file, where a user have some fields (words, transcriptions, definitions, examples, etc). When this user starts your application, the only he need to do is to link these fields from TXT to customized fields in your program (words to words, transcriptions to transcriptions, etc). This is because user can have limited set of fields in his dictionary. Like me, I need to have only 4 fields, such as words, definitions, transcriptions, and part of speech. But other people could have examples for each part of speech or more complicated structure.
d9 i4 H" A+ x+ w% UYour applications just parses TXT file to the program database, keeping in mind these links. The next step, based on the general logic of MDX source file to create a simple MDX (with help of MdxBuilder, for example). Style creation is also can be embedded to the applications using the same logic of linking users fields to program ones.
* L2 i) v) j. m! nAs for me MDX is not necessary feature, I just need simple dictionaries w\o any multimedia files. But these are my needs only.
3 Y/ y: l# @: L- V: |, q
0 o4 y: M' O% S: V# eThe same can be done when this application parses MDX to MDX source or text file. User could define which fields from MDX he need, what is the purpose of each field and get a final TXT or Excel file for the further processing. : v% B8 ~9 s( I% I: r
3 D8 }. D0 ?2 R3 j$ |4 v; c$ _8 ^
# X0 n7 O$ G) e# H: @& @6 |
|
|
