Hello Jean-Marc,
Sorry for my late reply.
- Original Message -
>> From: Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
>> To: 한창길 <[EMAIL PROTECTED]>
>> Cc: lyx-devel@lists.lyx.org
>> Date: 2006-12-29 21:13:56
>> Subject: Re: Input of CJK charact
> "한창길" == 한창길 <[EMAIL PROTECTED]> writes:
한창길> Hello,
한창길> I've found it very exciting that without CJK-patch, I can now
한창길> input CJK characters with lyx-1.5.0svn. However, viewing the
한창길> CJK characters (postscript or pdf) fails with the following
한창길> error messages:
한창길> "The output
On Tue, 2006-10-31 at 08:46 +0100, Georg Baum wrote:
> Add the proper encodings to lib/encodings and languages to lib/languages.
> Then you need to fix the frontend that all encodings from lib/encodings can
> be selected, currently the list is hardcoded in
> src/frontends/qt4/QDocumentDialog.C.
I
On Thu, 2006-11-02 at 11:55 +0100, Georg Baum wrote:
> > Can one just add utf-8 and expect it to work?
>
> As far as LyX is concerned: Yes. It is only commented out because it is a
> file format change.
Great! Let me try...
Will it be added in 1.5.0 ?
> But of course you can not expect that al
Gour wrote:
> On Tue, 2006-10-31 at 08:46 +0100, Georg Baum wrote:
>
>> Add the proper encodings to lib/encodings and languages to lib/languages.
>> Then you need to fix the frontend that all encodings from lib/encodings
>> can be selected, currently the list is hardcoded in
>> src/frontends/qt4/
On Thu, 2006-11-02 at 11:41 +0100, Gour wrote:
> I pulled the code from svn and will try to build it to see how well can
> LyX play with XeTeX...both Kile & Texmaker work with utf-8 so it will be
> pity if LyX is lacking proper support...
Ahh, some problems with my keyboard :-)
> Sincerely,
> G
On Tue, 2006-10-31 at 08:46 +0100, Georg Baum wrote:
> Add the proper encodings to lib/encodings and languages to lib/languages.
> Then you need to fix the frontend that all encodings from lib/encodings can
> be selected, currently the list is hardcoded in
> src/frontends/qt4/QDocumentDialog.C.
C
"한창길" wrote:
> Hello,
>
My bad 한창길, sorry for the confusion; sometimes I mix up the two writings
;-)
>
> No problem, but the problem is that I don't even know what the numbers in
> lib/encodings mean!!!
The numbers are gone in trunk. Only three names per encoding are left, they
are expl
Hello,
>>>My bad 한창길, sorry for the confusion; sometimes I mix up the two writings ;-)
No problem, but the problem is that I don't even know what the numbers in
lib/encodings mean!!!
Can anybody help?
Regards,
cghan
José Matos wrote:
On Tuesday 31 October 2006 10:04 am, Abdelrazak Younes wrote:
한창길 is the CJK patch maintainer :-)
Man... German, English, French, and now Chinese... I am impressed! :-)
You mean Korean, right?
My bad 한창길, sorry for the confusion; sometimes I mix up the two
writings ;-)
On Tuesday 31 October 2006 10:04 am, Abdelrazak Younes wrote:
> >
> > 한창길 is the CJK patch maintainer :-)
>
> Man... German, English, French, and now Chinese... I am impressed! :-)
You mean Korean, right?
> Abdel.
--
José Abílio
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Add the proper encodings to lib/encodings and languages to lib/languages.
Then you need to fix the frontend that all encodings from lib/encodings
can be selected, currently the list is hardcoded in
src/frontends/qt4/QDocumentDialog
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Add the proper encodings to lib/encodings and languages to lib/languages.
>> Then you need to fix the frontend that all encodings from lib/encodings
>> can be selected, currently the list is hardcoded in
>> src/frontends/qt4/QDocumentDialog.C.
>
>
Georg Baum wrote:
"한창길" wrote:
Hello,
I've found it very exciting that without CJK-patch, I can now input CJK
characters with lyx-1.5.0svn. However, viewing the CJK characters
(postscript or pdf) fails with the following error messages:
"The output file could not be closed properly. Probably
"한창길" wrote:
> Hello,
>
> I've found it very exciting that without CJK-patch, I can now input CJK
> characters with lyx-1.5.0svn. However, viewing the CJK characters
> (postscript or pdf) fails with the following error messages:
>
> "The output file could not be closed properly. Probably some ch
Hello,
I've found it very exciting that without CJK-patch, I can now input CJK
characters with lyx-1.5.0svn.
However, viewing the CJK characters (postscript or pdf) fails with the
following error messages:
"The output file could not be closed properly. Probably some characters of your
documen
16 matches
Mail list logo
