Hello
This patch adds support for different encodings to python parser.
Two options are added, --input-charset and --output-charset,
first one tells the parser to assume input documents (such as
URLs) to be in given encoding, _if it cannot be determined
automatically_ (so it does not override
On Wed, Feb 25, 2004 at 12:11:30AM -0500, Alexander R. Pruss wrote:
I'm thinking of adding a couple more transliteration tables to the search
(e.g., drop Latin2 accents, Cyrillic-ASCII, etc.; these are really handy
for users who don't want to pay for a localization to read some texts in a
On Fri, 27 Feb 2004, Radovan Garabik wrote:
Don't forget, that is you want enough generality, you have to allow
1-N scheme (e.g. one input char can be transliterated as a string
of more characters).
Yes, but then the searching will be significantly slower, or we will have
to have more than
On Fri, 27 Feb 2004, Radovan Garabik wrote:
Don't forget, that is you want enough generality, you have to allow
1-N scheme (e.g. one input char can be transliterated as a string
of more characters).
Alexander R. Pruss:
Yes, but then the searching will be significantly slower, or we
will
On Fri, 27 Feb 2004, Jewett, Jim J wrote:
Could you be more specific with the example?
For instance, if I'm reading something in French, and I want to look
for the word student, that could be represented as
eleve (assuming you have the same font)
e'l`eve (a common transcription)
eleve
---Reply to mail from Chris Hawks about Table changes
Massive changes to tables.
All calls to SafeMem(Handle/Ptr)New are in try{} blocks.
Improved error handling.
Anchors (and table icons) now displayed as 'normal' links (underline, etc)
Multiple anchors in a table cell.
Multiple
