On Thu, Mar 29, 2018 at 10:47 AM, Johan
wrote:
> Thank you Greg.
>
>
>
> I checked the other dictionaries, they all use the dictionary name as the
> file names.
>
>
>
> If changing the file names from “dict.xxx. to “ts2009en.xxx” violationing
> your SOP (standard operating procedures??), then I w
Thank you Greg.
I checked the other dictionaries, they all use the dictionary name as the file
names.
If changing the file names from “dict.xxx. to “ts2009en.xxx” violationing your
SOP (standard operating procedures??), then I would rather keep them as
“dict.xxx”.
Thank you for your
David,
I built the module without -c and the output files are still “dict.xxx”.
I was under the impression that using would encrypt the module
(protecting), but never understood why the is in a unprotected
.conf file.
Regards,
Johan
From: David Haslam
Sent: Thursday, 29 Ma
On Tue, Mar 27, 2018 at 2:51 AM, Johan wrote:
> Please help.
>
>
>
> I am using this command to create a SWORD dictionary module from TEI.
>
> tei2mod ./modules/lexdict/zld/ts2009en/ TS2009enVer100.txt -z -c ts2009en
>
>
>
> The output message is the following:
>
> tei2mod normalized 1 verses to
Johan,
Why do you want to encrypt your dictionary module?
Suggest first try building an unencrypted module without a ,
without using the -c option.
In any case, using "ts2009en" as the key is too easily crackable! It's only 8
characters long.
It wouldn't be of any value to protect intellectual
Thank you David for once again assisting me.
“ts2009en” is indeed the .
When I ran “./modules/lexdict/zld/ts2009en TS2009enVer100.txt -z -cts2009en”,
it gives me the error message:
You are running tei2mod: $Rev: 2138 $
tei2mod: Unknown argument: -cts2009en
It seems as if it doesn’t l
Johan,
Option -c expects the immediately after.
Because you followed it by the word "ts2009en" it assumed that was the
.
Here's the syntax help for the latest binary in Windows.
Observe that the [OPTIONS] are at the end of the command line.
You are running utils64\tei2mod: $Rev: 3416 $
TEI Lex