Put calls to ReinitializeWylieWordIfNecessary into the interlineal
key bindings (where they should have been all along). This may fix
some long-standing obscure interlineal bugs. It certainly fixes
one new problem (whereby interlinealHorizontalPadding was failing to
get initialized).
RFE #1104925. Now when you switch from TScript to OScript, or vice
versa, the code looks backward through the document to find the last
instance of the script type (T or O) and applies the formatting of
that last instance to the new text. If there was no previous
OScript, the "Normal" style parameters are used. This means that
the WylieWord Options dialog no longer needs or has OScript font
parameters. It retains the TScript font parameters, but these are
used as defaults only.
Implement SF RFE #1104920: New option (in Options dialog) to control
the horizontal whitespace in Interlineal mode.
Add new "Interlineal Tibetan" style for first row of Interlineal
matrices. Previously, Normal was used, but that meant user didn't
have control over vertical whitespace for first row.
Added 3 points of vertical space above the interlineal styles built
into the template. This makes them consistent with the styles that
are auto-defined by AddInterlinealStylesIfNecessary.
Diked defaultOScriptFontName (introduced 3 July to fix 1149498).
Replaced with literal "Times New Roman", which I think is clearer.
Motivated by the fact that this no longer *is* the default OScript
font (since that now comes from the Normal style).
document-changing operations (finished work on SF RFE #1151501,
modulo any bugs that may show up).
In interlineal mode, <space> now removes spaces before and after the
cursor before breaking up the cell.
In interlineal mode, add work-around for the Word bug whereby if you
insert a table in the line immediately after a table, it DWIMishly
merges the two. (Dealt with this by having alt+M insert a crlf to
keep the tables seperate.)
Conversion of TMW to Unicode now preserves styles.
When changing the Tibetan font in the Options dialog, its size and
position are heuristicated. This is fairly bogus, but will save
users who fail to RTFM much confusion. (Someone has already
reported the "bug" that TMW->Unicode conversion puts TScript text
above the Latin baseline.)
In installation, add warning about Outlook email editing interaction.
Explained Outlook email interaction bug.
Added discussion of how to uninstall.
Added Bob Chilton's explanation of the convoluted procedure
needed to make Tibetan line-breaking work properly. Included Cathy
Cantwell's caveat about re-application to existing documents.
Document that you shouldn't use a Tibetan IME with WW.
Addressing SF bug #951553 (interference with Outlook email editing):
put in a warning dialog that should catch (but not fix) the problem
Fixed SF 1149498: defined a public const whose value is "Times New
Roman" and replaced all Times font literals with it.
this workaround, when using TMW as TScript font, ]'<bsp>['g blew
out; the second ' came out in the wrong (TMW) font.
Changed type of variable "start" from Integer to Long in
InsertTibetanTshegBarAsUnicode. (Problem reported by Than Garson.)
Also fixed the analogous problem in InsertForeignTshegBarAsTScript.
SF bug [1151313]: AddInterlinealStylesIfNecessary failed to set the
font names. This bug could be duplicated by loading from Startup
and doing ]s<alt-m>s; the phonetics came out in TScript.
Add call to AddInterlinealStylesIfNecessary in
ConvertToInterlinealText to fix problem when running from Startup
(only). Problem reported by Cathy Cantwell.
oM was transcribed "ong" because I made M->ng for huM. But that was
totally bogus. This change means that huM comes out hum, which is
right for THDL (probably, although that is not well-defined) but
wrong for Aro. It's not possible to special-case huM for Aro
without adding another flag, and since the implementation of Aro
pronunciation is generally inaccurate, I'm going to punt for now.
Worked around newly-discovered Word bug that causes the selection
change event handler to get called spuriously. This caused bad
behavior in alt+m. Probably this bug has been around forever but
either no one noticed it or it was masked by something else.
Make HandleUserUCH call UpdateFromTransliteration, as needed.
Add code in InsertInterlinealMatrix to force OScript input in the
Wylie row.
Fixed 1118035 some more. Yesterday I fixed it for Unicode; I had
assumed this worked correctly for TMW, but it didn't, due to some
buggy version 1.1 legacy code. (So in fact this bug was in version
2.0 as well, but no one complained.)
Fixed SF bug 1118391: Now starts in OScript mode, not TScript.
Fixed SF bug 1119024: TCC->Unicode lost newlines and other whitespace.
Fixed SF bug 1149395: allow s+n+r as Tibetan stack.
Working on fix for 1119028 by modifying SelectionIsTScript, which is probably
in an inconsistent state currently.
Implement the (apparent) Unicode // misfeature: Whenever two U+0F0D
appear next to each other, by whatever means, they need to be
combined into a single U+0F0E.
Made MakeRangeTScript set .Font.NameBi, which seems to be necessary
on alternate Tuesdays.
Fix long-standing bug (was in 2.0, but I only just noticed it):
single-quote should be open-curly after newline and tab, as well as
after space. Probably after some other things as well, like magic
formatting codes, but it's too hard to figure out what.
Fix bug introduced by the optimization of font changes: TCC->Unicode
was failing to set the Unicode font, so everything came out Arial
Uni.
Fixed bug recently introduced in ProcessTibwn_iniLine that caused
Tibetan stacks not to work.
Fixed bug: when typing an OScript character, bombed if the
selection was not collapsed.
Fixed bug: _ was inserting 0020 rather than 00A0
Fixed bug that looks like it goes back at least to 2.0, that
inserting an alpha character in tscript after a symbol that has no
wylie (other than \uXXXX) bombs because the symbol is wrong counted
as CharOKinTshegBar. If it does go back to 2.0 I'm somewhat
surprised no one has noticed it; but probably these symbols are very
rarely used.
Moved text into "basic operation" that had somehow gotten stranded
in "EWTS".
Document new TCC-font-conversion feature.
Explain of USP10.DLL and hyperlink to discussion on thdl.org.
Hyperlink to EWTS documentation.
Hyperlink to THDL simplified phonetics document on thdl.org.
Added note about pecha preparation.
Changed TOC to a more-nearly-standard form, with page numbers,
ergo suitable for print as well as on-line reading.
Replace some literal URLs with hyperlinks.
Remove the following text: "WylieWord does not support the EWTS
-i+thi transliteration. (You can get this rare glyph using a
Unicode escape, however.)" Apparently this transliteration has
been removed from EWTS (thankfully); it's now only \uF042.
They should not be decomposed on transliteration.
Made 0F0E (//) a "symbol" rather than "combination".
Made the Sanskrit aspirates and k+Sh into foreign consonants,
rather than "combination"s. This doesn't actually affect the
current code, but better reflects what it is doing (after the
change to canonicalize these as single "precomposed" characters).
Made the "strongly disrecommended" vowel signs "deprecated" rather
than "combination".
Code-cleaned ReadTMWdefinitionFile which was an awful mess. Did
this along the way when implementing TCC 8-bit support.
Unicode<->TMW conversion of whole document now applies to footnotes
and endnotes.
Now (per spec) use 00A0 space rather than 0020 (= ASCII 32) for EWTS _ .
Implemented [] nesting rule for F9. It already worked for F10,
fortuitously.
Optimize out most calls to MakeRange*Script (recently introduced to
work around Word Unicode font-change bug); this improves performance
and also decreases the number of useless font-change events on the
Undo list.
"combination" -> "deprecated" in Unicode definition reader.
for experimental Unicode extensions. It's now clear that Unicode is
going in the trunk -- in fact I'm close to a first beta release -- so
I'm clobbering the "Unicode hackup.dot" file and checking in its
latest version here.
The changes:
Unicode support. Extensive remodularization and code changes in most
parts of the system, far too much to detail here. 2.1 has roughly a
third more code than 2.0!
Per request of Cathy Cantwell, make F9 on body text that includes
footnotes/endnotes convert text of said notes.
In support of the previous, various changes to make Tibetan work in
footnotes (and endnotes) generally.
Pronunciation function now talks about "foreign" words rather than
"Sanskrit"; former is more generally correct.
Fixed prehistoric bug (goes back to Than's version 1.1) that I just
found: F6 went to end of document if you hit Cancel.
Fixed SourceForge bug 941183: literal curly quotes in VBA screwed up
Chinese Word. (Need to get Jeff Wu to verify fix -- I couldn't
duplicate bug.)
Fixed SourceForge bug 986847: double quote doesn't curlify. I
"fixed" this by removing the double-quote binding. That's not the
optimal fix, but the only thing that's non-optimal about it is that
when you are typing EWTS, double-quote self-inserts rather than
telling you that it's not a valid EWTS character.
Fixed SourceForge bug 986850 (Interlineal failing when loaded from
Startup, due to an instance of the Word bug where Startup-loading
doesn't run initializations)
Fixed bug: in F9 conversion, \u allowed only lower-case (not
upper-case) alpha hex digits.
Fixed bug: in F9 conversion, \ was not interpreted as an escape
within [].
Fixed bug: \Z] did not return to TScript, but instead inserted the
].
Fixed bug: [ and ], when in Interlineal mode, now beep rather than
screwing things up.
Various uses of "English" replaced in the UI. (Trying to be less
ethnocentric; we have lots of users whose primary language is not
English.)
