ROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 2:24 PM
Subject: RE: [sword-devel] beta 1.5.2 WIN32 binary available
> Looks like it's very buggy, though which of these are particular to me
> and which are real bugs I can't say having only tested on one machi
2001 10:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [sword-devel] beta 1.5.2 WIN32 binary available
>
> Ok, Call me stupid but how can I obtain a Chineese font (or other
fonts
> for
> unicode modules for that matter) to test these with? Also which
modules
> should I download
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-sword-
> [EMAIL PROTECTED]] On Behalf Of Troy A. Griffitts
> Sent: Saturday, June 09, 2001 1:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [sword-devel] beta 1.5.2 WIN32 binary available
>
> Well, I h
I have noticed that in the latest Beta that the Chineese(UTF8) and Greek
(LXXM) fonts work on two boxes at my office. At home however I cannot get
the Chineese to show up at all, but the Greek does. Both machines are
Windows NT with Internet Explorer 5.5 and w/ the additional Chineese fonts
instal
OK, new InstallMgr.exe binary available. I switched over to the
Jedi-Indy project FTP component. It's included in Kylix also and we
were havin' troubles with the current FTP component anyway. So, tell me
if ya have any troubles with remote installs, please:
http://www.crosswire.org/sword/ALPHA
> OK, new InstallMgr.exe binary available. I switched over to the
> Jedi-Indy project FTP component. It's included in Kylix also and we
> were havin' troubles with the current FTP component anyway. So, tell me
> if ya have any troubles with remote installs, please:
Nice to hear we are trying a
> > OK, new InstallMgr.exe binary available. I switched over to the
> > Jedi-Indy project FTP component. It's included in Kylix also and we
> > were havin' troubles with the current FTP component anyway. So, tell me
> > if ya have any troubles with remote installs, please:
>
> Nice to hear we a
Thanks, everyone, for all the bug reports! Got 2 new binaries ready:
http://www.crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/sword.exe
http://www.crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/InstallMgr.exe
Hope we got all the bugs you all mentioned.
-Troy.
as to be
highlighted. And LXXM still shows garbage in the new testament.
In Christ,
David
- Original Message -
From: "Troy A. Griffitts" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 17, 2001 2:27 PM
Subject: Re: [sword-devel] beta 1.5.2 WIN32 binary ava
I'll try to fix by this
evening.
--Chris
> - Original Message -
> From: "Troy A. Griffitts" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 17, 2001 2:27 PM
> Subject: Re: [sword-devel] beta 1.5.2 WIN32 binary available
>
>
InstallMgr
When I Refresh from Remote Source, it now says
downloading 35040 of 0 (3504100%)
All files for "Murdock" were downloaded and installed perfectly.
For FinPR, The letter after "Phy" in the modules description "1938 PhyZ Raamattu"
appears as a black block.
Sword Windows Frontend
"Hide
> For FinPR, The letter after "Phy" in the modules description
> "1938 PhyZ Raamattu" appears as a black block.
I think that's a Z with a breve, a high ascii character that has a
tendency to cause problems. But hey, that's the module name, what can
we do?
> I think that InstallMgr should remo
> > For FinPR, The letter after "Phy" in the modules description
> > "1938 PhyZ Raamattu" appears as a black block.
>
> I think that's a Z with a breve, a high ascii character that has a
> tendency to cause problems. But hey, that's the module name, what can
> we do?
Just noticed it, so thought
> I discovered later this afternoon that removing the module's corresponding
line from the [TextView] section of layout.conf solves
> the problem.
>
> So my ideas now are that installing or updating a module could set the
line in that file to "true", removing a module could remove
> the line from
> > > For FinPR, The letter after "Phy" in the modules
> description "1938
> > > PhyZ Raamattu" appears as a black block.
> >
> > I think that's a Z with a breve, a high ascii character that has a
> > tendency to cause problems. But hey, that's the module
> name, what can
> > we do?
>
> Ju
> Can anyone tell me what could be
> different. How does it find the correct Unicode font without choosing
it
> explicitly?
I'll take a stab at this, but I'm mostly guessing. I think when you
install language packs, Windows "learns" how to handle those languages.
So, where the Chinese works, you
16 matches
Mail list logo
