"Asger K. Alstrup Nielsen" wrote:
> > > However, FYI, XForms cannot draw 16 bit character strings.
> >
> > I just remembered that in CLE (Chinese Linux Externsion) package, they
> > manage to display Chinese in LyX. Or is it KLyX?
>
> The canvas area in LyX is not drawn using XForms, but w
> > However, FYI, XForms cannot draw 16 bit character strings.
>
> I just remembered that in CLE (Chinese Linux Externsion) package, they
> manage to display Chinese in LyX. Or is it KLyX?
The canvas area in LyX is not drawn using XForms, but with raw X11
calls. The problem remains for th
"Seak, Teng-Fong" <[EMAIL PROTECTED]> wrote:
> As there're a significant number of LyX users under Windows, some of
> them might want to contribute to the translation too. Imagine the trouble
> they would encounter when some of them edit the translation file under Unix
> while others under
Shigeru Miyata wrote:
> > Actually, newer versions of XFree86 support already natively Unicode, so
> > do a lot of commercial X (if not all).
>
> It also introduces Big5 support. Other multibyte encodings have been
> supported for quite some time.
Yup, I know that. I just mentioned Unicod
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > About i18n, I've read the "encoding.lyx" article written by Asger
| > Alstrup Nielsen. (By the way, the file is no longer available at the URL
| > where I got it before. Is it no longer available?) The article is
|
| Good quest
"Seak, Teng-Fong" <[EMAIL PROTECTED]> wrote:
> Actually, newer versions of XFree86 support already natively Unicode, so
> do a lot of commercial X (if not all).
It also introduces Big5 support. Other multibyte encodings have been
supported for quite some time.
>
Lars Gullik Bjønnes wrote:
> Note that we cannot live with that way of updating po files, most of
> the po files miss a lot to work ok with the current lyx sources.
Yeek, I know, I'm a bit stuffed with work. When is 1.1.4 scheduled?
I'll try to overhaul the menu stuff till then...
Pit
--
~
> About i18n, I've read the "encoding.lyx" article written by Asger
> Alstrup Nielsen. (By the way, the file is no longer available at the URL
> where I got it before. Is it no longer available?) The article is
Good question. Lgb, what happened with the old ftp.devel.lyx.org content?
About i18n, I've read the "encoding.lyx" article written by Asger
Alstrup Nielsen. (By the way, the file is no longer available at the URL
where I got it before. Is it no longer available?) The article is
talking about strings and encodings in LyX v1.2. Regarding this article
and i18n/l
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | Also, when we have the new menu code, we will no longer lose
Lars> an entire | menu because an entry is not translated.
Lars> True but this is not for menucode only. po file translators
Lars> seems to thing that their work i
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
| Lars> > "Soeren" == <" <[EMAIL PROTECTED]>> writes: | | Soeren> The
| Lars> export Menu is in the german version s
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> > "Soeren" == <" <[EMAIL PROTECTED]>> writes: | | Soeren> The
Lars> export Menu is in the german version still showing english |
Lars> Soeren> names. I thing it's bec
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Soeren" == <" <[EMAIL PROTECTED]>> writes:
|
| Soeren> The export Menu is in the german version still showing english
| Soeren> names. I thing it's because of same shortcoming in de.po
|
| Hello,
|
| Thanks for the report. I updated
> "Soeren" == <" <[EMAIL PROTECTED]>> writes:
Soeren> The export Menu is in the german version still showing english
Soeren> names. I thing it's because of same shortcoming in de.po
Hello,
Thanks for the report. I updated de.po.
JMarc
The export Menu is in the german version still showing english names. I thing it's
because of same shortcoming in de.po
#: src/menus.C:489
#, fuzzy
msgid ""
"Export%t|as LaTeX...%x40|as DVI...%x41|as PostScript...%x42|as Ascii "
"Text...%x43|as HTML...%x44|Custom...%x45"
msgstr ""
"Exportieren%t
" " <[EMAIL PROTECTED]> writes:
| Ok I compiled 1.1.2 with the - - with-included-gettext and - -
| with-catgets flags and now I got german menus. Am I supposed to do
| this always? In 1.0.4 it worked
| without it (just checked it against 1.1.2).
|
| Soeren
You should not need the --with-catge
Ok I compiled 1.1.2 with the - - with-included-gettext and - - with-catgets flags and
now I got german menus. Am I supposed to do this always? In 1.0.4 it worked
without it (just checked it against 1.1.2).
Soeren
17 matches
Mail list logo
