Messages

I tested it.  Everything works great.  Thank you very much

Jeff

Hmm, it still doesn't work.  I got this error again:

Thrown de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException: C
lass could not be loaded: de.kugihan.dictionaryformids.translation.normation.Nor
mationBul / Class could not be loaded: de.kugihan.dictionaryformids.translation.
normation.NormationBul

I looked inside DictionaryForMIDs.jar and saw the 3 new files.

Do I need a new version of DictionaryGeneration with the new normation classes?  At the end of the error message it refers to DictionaryGeneration.java:

at de.kugihan.dictionaryformids.dictgen.DictionaryGeneration.main(DictionaryGeneration.java:95)


Here is the full error message:
Thrown de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException: C
lass could not be loaded: de.kugihan.dictionaryformids.translation.normation.Nor
mationBul / Class could not be loaded: de.kugihan.dictionaryformids.translation.
normation.NormationBul

de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException: Class co
uld not be loaded: de.kugihan.dictionaryformids.translation.normation.NormationB
ul
        at de.kugihan.dictionaryformids.dataaccess.DictionaryDataFile.getObjectF
orClass(DictionaryDataFile.java:306)
        at de.kugihan.dictionaryformids.dataaccess.DictionaryDataFile.initValues
(DictionaryDataFile.java:257)
        at de.kugihan.dictionaryformids.general.UtilWin.readProperties(UtilWin.j
ava:36)
        at de.kugihan.dictionaryformids.dictgen.DictionaryGeneration.main(Dictio
naryGeneration.java:95)
Thrown de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException: C
lass could not be loaded: de.kugihan.dictionaryformids.translation.normation.Nor
mationBul / Class could not be loaded: de.kugihan.dictionaryformids.translation.
normation.NormationBul

de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException: Class co
uld not be loaded: de.kugihan.dictionaryformids.translation.normation.NormationB
ul
        at de.kugihan.dictionaryformids.dataaccess.DictionaryDataFile.getObjectF
orClass(DictionaryDataFile.java:306)
        at de.kugihan.dictionaryformids.dataaccess.DictionaryDataFile.initValues
(DictionaryDataFile.java:257)
        at de.kugihan.dictionaryformids.general.UtilWin.readProperties(UtilWin.j
ava:36)
        at de.kugihan.dictionaryformids.dictgen.DictionaryGeneration.main(Dictio
naryGeneration.java:95)

I can help you with the Chinese CEDICT dictionary.  The dictionary can already search in pinyin.  I included the readme from the CEDICT dictionary.

Here is a little bit of the readme:
Chinese is entered using pinyin with tone numbers (e.g. 'ni3 hao3') or without tone numbers (e.g. 'ni hao').  You must enter a space between each word.  For example, 'ni3 hao3' will produce search results, whereas 'ni3hao3' will not produce results.

Jeff

Hmm, it did not work.  I got this error:
Thrown de.kugihan.dictionaryformids.general.DictionaryClassNotLoadedException:
Class could not be loaded: de.kugihan.dictionaryformids.translation.normation.Nor
mationBul / Class could not be loaded: de.kugihan.dictionaryformids.translation.
normation.NormationBul

I looked inside verison 3.5.6 of DictionaryForMIDs.jar:
DictionaryForMIDs.jar\de\kugihan\dictionaryformids\translation\normation\

But, I did not see normationBul.class, normationCyr1.class, or normationCyr1.class in the directory.

Should the new normation files be there?  Or did I make a mistake?  Or do I need a new version of DictionaryGeneration too?

You just added the feature to remove the BOM from dictionary_input.csv files because the first entry of every dictionary was not indexed before (this was fixed while we were updating the Chinese normation class).  But, this new problem is to remove the BOM from reading the normation java files (NormationEng2.java, normationRus2.java, etc).

Thanks.  Filtering out the BOM is not a high priority.  Just, if you have the chance, it'd be nice to add the feature.

Jeff

You mean that the normation classes should filter out the BOM-character ?

Yes, I think that would be good.  Other people in the future may write normation classes with a BOM.  Personally, I save all UTF-8 files with a BOM.  Then the file is guaranteed to open correctly in programs.

I uploaded a new version here:
http://prdownloads.sourceforge.net/dictionarymid/DictionaryForMIDs_3.5.0(beta4).zip?download

I added the PAUSE to the setup.bat file and edited the newdict.html file.  I think this is the final version.  I've done everything I think we need for Windows users.

I added this at the top of newdict.html:
Note: these are instructions for Windows users.  Detailed instructions are coming soon for other operating systems.  For the time being, just use the build.sh file instead of the setup.bat file.

I think Linux and Mac users can follow the instructions for the time being.  There are not many differences.

Is this ready to be official?  Should I change newdict.html on the website to the new instructions?  And should I upload a final version and direct users to download the new ZIP file with all the tools?

Or should we wait until detailed instructions for Linux & Mac are written?

I did some research.  I noticed there was 1 difference between the new normation classes and the old NormationRus2.java:
NormationRus2.java does not have a BOM
I put a BOM in the new normation classes

The UCN for the BOM is \uFEFF, the HTML is &#65279.

I re-saved the normation classes with no BOM now.  They should work OK now.

Maybe sometime in the future, it would be nice to support a BOM in DfM normation classes.  But, it's a low priority.

Jeff

Just for reference, here are the normation classes.  This might save someone the work of learning it later.

Cyrillic     NormationCyr1     NormationCyr2     NormationBul
а     a     a     a
б     b     b     b
в     v     v     v
г     g     g     g
д     d     d     d
е     e     e     e
ё     jo     yo
ж     zh     zh     zh
з     z     z     z
и     i     i     i
й     j     j     y
к     k     k     k
л     l     l     l
м     m     m     m
н     n     n     n
о     o     o     o
п     p     p     p
р     r     r     r
с     s     s     s
т     t     t     t
у     u     u     u
ф     f     f     f
х     h     h     h
ц     c     c     ts
ч     ch     ch     ch
ш     sh     sh     sh
щ     shh     shh     sht
ъ     "     "     aj     aj
ы     y     y
ь     x     x     x
э     eh     eh
ю     ju     yu     yu
я     ja     ya     ya
і     ij     ij
ѳ          fh
ѣ          je
ѵ          yh
ґ     gj     gj
ѓ     gj     gj
є     ye     ye
ї     yi     yi
ѕ     dz     dz
ј     jj     jj
љ     lj     lj
њ     nj     nj
ќ     kj     kj
џ     dj     dj
ў     uj     uj

Gert

Can you please add these 3 normation classes to the next version of DfM?  They are for Cyrillic.
- NormationCyr1.java   (Russian, Ukrainian, Macedonian)
- NormationCyr2.java   (Russian, Ukrainian, Macedonian)
- NormationBul.java     (Bulgarian)

NormationCyr1.java replaces NormationRus2.java and NormationUkr.java.
NormationCyr2.java replaces NormationRusC.java and NormationUkrC.java.

I fixed a few errors in the transcriptions and added some missing transcriptions from the old normation classes.  We can keep NormationRus2.java, NormationUkr.java, NormationRusC.java, and NormationUkrC.java in DfM for the Czech dictionaries.  But, we can remove the information from newdictNormationLang.html.

Once the new normation classes are added to DfM. I'll edit newdictNormationLang.html to show the new normation classes.

Jeff

The [ ] were only for the content declarations:
[01 ... ]

Sorry, yesterday I looked at indexChi1.csv and everything looked good.  But today I used the dictionary in an emulator.  I found a new problem.  Now all the pinyin transcription is in [ ].

Inside directory1.csv is:
懶洋洋 [01\[ lǎn yáng yáng\]]     malvigla; langvora

It is displayed in the emulator as:
懶洋洋 [ lǎn yáng yang]
malvigla; langvora

It should look like:
懶洋洋  lǎn yáng yang
malvigla; langvora

Can you please remove the [ ] from the transcription display?  There is no rush.

Yes, everything works now.  The BOM was removed from the first entry.  The {{}} work correctly.  And the ExpressionSplitString works correctly.

Thank you very much
Jeff

No problem.  There is no rush.