Jean-Marc Lasgouttes wrote:
> And you list supports these two mechanisms, right?
yes. it takes the list of "encodable" chars from Encoding.cpp, which is
built from these informations.
Jürgen
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>
>> Why is it limited this way? I thought that our output mechanism was
>> able to take care of translations...
>
> Our unicodesymbols list only supports a subset of translations from unicode
> chars to their LaTeX rep
Jean-Marc Lasgouttes wrote:
> Why is it limited this way? I thought that our output mechanism was
> able to take care of translations...
Our unicodesymbols list only supports a subset of translations from unicode
chars to their LaTeX representations (in the given encoding). Furthermore,
we can ou
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> the range of available symbols is limited by the document encoding (+
> unicode symbols defined in the unicodesymbols file). You'll get all if you
> select utf-8 (but then the dialog becomes rather slow).
Why is it limited this way? I thought tha
Pavel Sanda wrote:
> would you be oposed to put such kind of label or tooltip somewhere in
> symbols dialog?
No. Furthermore, it should be documented in the Help files.
Jürgen
> > this should be documented
> > somewhere, i would otherwise think this dialog shows all characters
> > posible to lyx ever.
>
> the range of available symbols is limited by the document encoding (+
> unicode symbols defined in the unicodesymbols file). You'll get all if you
> select utf-8 (but
Pavel Sanda wrote:
> and you mean document encoding, right?
yes.
> this should be documented
> somewhere, i would otherwise think this dialog shows all characters
> posible to lyx ever.
the range of available symbols is limited by the document encoding (+
unicode symbols defined in the unicod
> This depends on the used encoding. In general, all can be used (and the list
> is far from being complete).
aha, ok.
and you mean document encoding, right? this should be documented somewhere, i
would otherwise think this dialog shows all characters posible to lyx ever.
pavel
Pavel Sanda wrote:
>> on another note - it is really annoying to have ALL unicode blocks
>> translatable when only 10% is used. this is waste of translators time.
>> can be the used blocks determined beforehead?
> moreover it seems translation of these strings do not appear in gui.
This depends o
Pavel Sanda wrote:
> guisymbols combo is too small. i will commit this if no objections.
Not from me.
Jürgen
> on another note - it is really annoying to have ALL unicode blocks
> translatable when only 10% is used. this is waste of translators time.
> can be the used blocks determined beforehead?
moreover it seems translation of these strings do not appear in gui.
pavel
> hi,
> guisymbols combo is too small. i will commit this if no objections.
on another note - it is really annoying to have ALL unicode blocks
translatable when only 10% is used. this is waste of translators time.
can be the used blocks determined beforehead?
pavel
hi,
guisymbols combo is too small. i will commit this if no objections.
pavel
diff --git a/src/frontends/qt4/ui/SymbolsUi.ui
b/src/frontends/qt4/ui/SymbolsUi.ui
index 7f3cd1b..2b4b907 100644
--- a/src/frontends/qt4/ui/SymbolsUi.ui
+++ b/src/frontends/qt4/ui/SymbolsUi.ui
@@ -47,7 +47,11 @@
13 matches
Mail list logo
