This is something for a future release... just some food for thought.
Especially for dictionaries, it would be very convenient to match the
user's search key against the whole string instead of matching against
the beginning only.
Consider the following three english entries in CEDICT:
(doubl
>This standard is necessary for problems exactly as the one you've
>experienced in the win32 frontend. These are internal names that need
>to be usable in standard encoding mechanisms such as programming
Then I strongly vote for adding an optional Displayname= or something
like that to the co
>>[a-z,A-Z,0-9,_] are the only valid characters in module names. The
>>module name should be changed.
>
>
> Because?
This standard is necessary for problems exactly as the one you've
experienced in the win32 frontend. These are internal names that need
to be usable in standard encoding mec
On Thu, 1 Aug 2002, Troy A. Griffitts wrote:
> [a-z,A-Z,0-9,_] are the only valid characters in module names. The
> module name should be changed.
Because?
Your standard looks rather arbitrary since this is the only problem I have
yet witnessed due to a module name with a tilde. Minimally i
[a-z,A-Z,0-9,_] are the only valid characters in module names. The
module name should be changed.
Chris Little wrote:
> Okay, I'm pretty behind in all the bug reports, so forgive me if this has
> been reported already.
>
> LDs (and possibly other modules) with a ~ in the module name cause an
Okay, I'm pretty behind in all the bug reports, so forgive me if this has
been reported already.
LDs (and possibly other modules) with a ~ in the module name cause an
error on load. The error reads: "LexDictRTFERaf~en" is not a valid
component name. (ERaf~en is the module name.) I think we
> You need Borland's C++Builder at least version 5. I think we should
> compile on the free/almost-free personal edition, but I use the
> profesional edition. You DON'T need the enterprise edition. Can
> anyone confirm that the personal version does indeed work? I think
> it is like $69 b
Stephen,
> Many of the bugs I've reported are still not fixed
Yep, you are very thorough in your reports! We seem to hit the most
critical bugs first and many things you report are things that would be
nice to fix, but are not necessarily showstoppers. All that to say
THANKS FOR REPORTING T
Sounds like a great idea, assuming we can get someone to coordinate/write
it all. We can use/promote the existing sword-info mailing list for this
purpose.
--Chris
(BTW, sorry that our Feature of the Month is almost 2 months old. I'm
very busy with school right now, but I have a new feature
Bill Crossley wrote:
> Greetings,
>
> Thank you. I can now save personal commentary entries under windows 98. I have
>noticed some other bugs that seem new to beta S. They are:
>
> 1. Sword crashes intermittently when trying to exit after saving / modifying a
>personal commentary entry. At
Greetings,
Thank you. I can now save personal commentary entries under windows 98. I have
noticed some other bugs that seem new to beta S. They are:
1. Sword crashes intermittently when trying to exit after saving / modifying a
personal commentary entry. At one point, it crashed on saving
Greetings all. New to the list, so I apologize if this question has
been addressed previously. (I did look at the archive though..)
I see that there is a module for accessing the API from Perl, but has
anyone done anything with PHP?
I see a lot of CMS packages in use using php and am planni
On Thu, 01 Aug 2002 19:07:01 +0600
[EMAIL PROTECTED] wrote:
Hi,
> For getting the FS path of a module, new function
>
> virtual SWModule::getPath()
>
> is needed. I will create and send the patch for it. OK?
module->getConfigEntry("AbsoluteDataPath") ?
> P.S. How about some info about algor
Hi,
I want to compress (in the sense of eliminating empty entries) modules
in-place. For this I need to create a new module in the /tmp directory and
copy old module to the new one.
But what to do after this for copying the new module to the place of the old
one? The best solution seems to be
> I think we're getting close. There are many suggestions we haven't
> implemented and want to, but I think we have most all the bugs licked.
> Keep your great feedback coming.
Many of the bugs I've reported are still not fixed, eg font size chosen for
LD index, search results column resizing le
There have been some discussion some time ago how to make Sword more
known and some people showed up with some ideas. I don't know what
happened with this and thought about how good is information spreading
about Sword and its projects itself. As I am subscribed to serveral
lists concerning Sword
16 matches
Mail list logo
