On Tue, Oct 17, 2023 at 01:01:31PM -0400, Richard Kimberly Heck wrote:
> On 10/9/23 14:42, Pavel Sanda wrote:
> >On Fri, Sep 08, 2023 at 04:05:49PM -0400, Richard Kimberly Heck wrote:
> >>I am planning to freeze strings once we have had some initial feedback on
> >>beta 5 and make sure that there a
Am Montag, dem 23.10.2023 um 06:16 +0200 schrieb Jürgen Spitzmüller:
> Thanks. So its the "pat" regex in qt_l10n (lyx_pot.py) that is to
> blame. Shouldn't be too hard to fix that to consider line breaks
> within ..., no?
Correcting myself after trying: \n in ui file strings do not seem to
work.
Am Sonntag, dem 22.10.2023 um 19:34 +0200 schrieb Enrico Forestieri:
> Instead of "" you can also use the entity "
". The
> difference
> is that this is directly replaced by lyx_pot.py to "\n" so that Qt
> will
> not use the html parser simply for introducing a newline char.
Thanks. So its the "
On Sun, Oct 22, 2023 at 01:22:05PM +0200, Jürgen Spitzmüller wrote:
Am Sonntag, dem 22.10.2023 um 12:33 +0200 schrieb Dan:
Just for the record and out of curiosity, what was the problem with
that string? I see you just added a line break HTML element to it,
and suddenly it appears in the POT fi
22 d’oct. de 2023, 13:21 per sa...@lyx.org:
> On Sun, Oct 22, 2023 at 01:06:58PM +0200, Dan wrote:
>
>> Sorry, I did not intend to mean or hint you all should wait until I am done.
>> The strings I noted as "problematic" are, in my opinion, not that important:
>> little type errors and improvab
Am Sonntag, dem 22.10.2023 um 12:33 +0200 schrieb Dan:
> Just for the record and out of curiosity, what was the problem with
> that string? I see you just added a line break HTML element to it,
> and suddenly it appears in the POT file. Has something to do with QT
> or with Gettext?
>
> Will appre
On Sun, Oct 22, 2023 at 01:06:58PM +0200, Dan wrote:
> Sorry, I did not intend to mean or hint you all should wait until I am done.
> The strings I noted as "problematic" are, in my opinion, not that important:
> little type errors and improvable UX. Also, there are just a few.
> I encounter them
22 d’oct. de 2023, 12:51 per sa...@lyx.org:
> On Sun, Oct 22, 2023 at 12:21:41PM +0200, Dan wrote:
>
>> >> I must object :). I have come across some strings of the UI that should
>> >> be changed. For now I am only notifying the following two, which I think
>> >> are important; the rest I will
On Sun, Oct 22, 2023 at 12:21:41PM +0200, Dan wrote:
> >> I must object :). I have come across some strings of the UI that should be
> >> changed. For now I am only notifying the following two, which I think are
> >> important; the rest I will report in bulk when done with the translation.
> >>
>
21 d’oct. de 2023, 12:53 per jspi...@gmail.com:
> Am Samstag, dem 21.10.2023 um 10:38 +0200 schrieb Dan:
>
>> 2. There is a tooltip that is not translatable: it does not appear
>> in the POT file. Thus, it shows in English in the interface. To see
>> what I mean do the following
>> 1. Open a
21 d’oct. de 2023, 22:15 per sa...@lyx.org:
> On Sat, Oct 21, 2023 at 10:38:36AM +0200, Dan wrote:
>
>> I must object :). I have come across some strings of the UI that should be
>> changed. For now I am only notifying the following two, which I think are
>> important; the rest I will report in
On Sat, Oct 21, 2023 at 10:38:36AM +0200, Dan wrote:
> I must object :). I have come across some strings of the UI that should be
> changed. For now I am only notifying the following two, which I think are
> important; the rest I will report in bulk when done with the translation.
What's your es
Am Samstag, dem 21.10.2023 um 10:38 +0200 schrieb Dan:
> 1. Language (in the settings dialog of a listing inset). In English
> this word can be used to refer to both, a tongue and a programming
> language. In other languages this is not necessarily the case, for
> instance in Spanish
> - Langua
On 10/9/23 14:42, Pavel Sanda wrote:
On Fri, Sep 08, 2023 at 04:05:49PM -0400, Richard Kimberly Heck wrote:
I am planning to freeze strings once we have had some initial feedback on
beta 5 and make sure that there aren't any issues there that need a string
change. We're waiting at the moment for
Am Montag, dem 09.10.2023 um 20:42 +0200 schrieb Pavel Sanda:
> > 5. The string "Table" appears in quite some contexts that are
> > contradicting: in some it really means Table, while in others it
> > actually means "Tabular". Remember that Table/Tabular are related
> > in the same way Figure/Imag
On Sat, Sep 16, 2023 at 09:16:37PM +0200, Dan wrote:
> > I have three suggestions.
> > 1. Tools > Preferences > Document Handling > Display single close-tab
> > button. The tooltip states that, if checked, a single close-tab button will
> > appear on the "left corner", but it actually appears on
On Fri, Sep 08, 2023 at 04:05:49PM -0400, Richard Kimberly Heck wrote:
> I am planning to freeze strings once we have had some initial feedback on
> beta 5 and make sure that there aren't any issues there that need a string
> change. We're waiting at the moment for the Windows installer.
Riki, how
> I am planning to freeze strings once we have had some initial feedback on
> beta 5 and make sure that there aren't any issues there that need a string
> change. We're waiting at the moment for the Windows installer.
>
> That said, if there are any changes you want to get into 2.4.0 that invol
Le 01/02/2012 16:22, Xu Wang a écrit :
What compiler are you using Jean-Pierre?
Here you are:
$ lyx-2.0.3svn -version
LyX 2.0.3svn (not released yet)
Built on Jan 31 2012, 18:39:32
Configuration
Host type:i686-pc-linux-gnu
Special build flags: build=developme
On Wed, Feb 1, 2012 at 3:01 AM, Jean-Pierre Chrétien <
jeanpierre.chret...@free.fr> wrote:
> Le 31/01/2012 16:45, Richard Heck a écrit :
>
>
> Translators, please prepare for 2.0.3. I am tentatively planning to
>> prepare the release on 16 February, so if you could have your new po
>> files in by
Jean-Pierre Chrétien writes:
| Le 31/01/2012 16:45, Richard Heck a écrit :
>
>> Translators, please prepare for 2.0.3. I am tentatively planning to
>> prepare the release on 16 February, so if you could have your new po
>> files in by 15 February, I'd appreciate it.
>
| For testing against shortc
Le 31/01/2012 16:45, Richard Heck a écrit :
Translators, please prepare for 2.0.3. I am tentatively planning to
prepare the release on 16 February, so if you could have your new po
files in by 15 February, I'd appreciate it.
For testing against shortcuts conflicts, I compliled 2.0.3svn, I noti
hi,
please can somebody explain me what is meant by the string
"try to reconfigure using only the defaults"
inside
"LyX will only have minimal functionality because no textclasses have been"
"found. You can either try to reconfigure LyX normally, try to reconfigure"
"using only the defaults, or
> "Bjarke" == Bjarke Roune <[EMAIL PROTECTED]> writes:
Andre> Most people want to get their job done. If they get it done in
Andre> 28 instead of 36 minutes they are usually happy...
>>
Bjarke> Hmm... I don't understand why std::string is so much worse. Is
Bjarke> it solely because it is a te
"Bjarke Roune" <[EMAIL PROTECTED]> writes:
| Hmm... I don't understand why std::string is so much worse. Is it solely
| because it is a template, and some compilers can't handle those as well as
| non-templates?
likely.
| It would seem the ideal place to fix this would be on the compiler side o
On 20-Feb-2002 Jean-Marc Lasgouttes wrote:
> This is what I had in mind, indeed. You've got to find a bufferview
> somewhere. And probably an inset should be able to know in which
> bufferviews it belongs (I assume it could do that by knowing in which
> document it belongs)
Yes document or we w
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> On 20-Feb-2002 Jean-Marc Lasgouttes wrote:
>> What bufferview would you use with your lfun solution? If you know
>> that, you can just use the same...
Juergen> This doesn't matter as in the case of multiple bufferviews
Juerge
On 20-Feb-2002 Jean-Marc Lasgouttes wrote:
> What bufferview would you use with your lfun solution? If you know
> that, you can just use the same...
This doesn't matter as in the case of multiple bufferviews the lyxfunc
aproach would also be wrong: owner()->view() which view??? We now have
only
On Wednesday 20 February 2002 3:30 pm, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
>
> Angus> Should I modify GCache::update from void
> Angus> GCache::update(InsetGraphics const &); to void
> Angus> GCache::update(InsetGraphics const &, BufferView
On Wednesday 20 February 2002 2:16 pm, Juergen Vigna wrote:
> On 20-Feb-2002 Angus Leeming wrote:
>
> > So how should I proceed. Somehow I need to tell the underlying bufferview
> > that the inset has changed. That is, I'll have to call
> > BufferView::updateInset(Inset *, false)
> >
> >
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Should I modify GCache::update from void
Angus> GCache::update(InsetGraphics const &); to void
Angus> GCache::update(InsetGraphics const &, BufferView const *);
Angus> and store which BufferView the inset is to be found in. Only
On 20-Feb-2002 Angus Leeming wrote:
> So how should I proceed. Somehow I need to tell the underlying bufferview
> that the inset has changed. That is, I'll have to call
> BufferView::updateInset(Inset *, false)
>
> The question is how?
I would say as proove of concept you can use curren
On Wednesday 20 February 2002 2:45 pm, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> When the loading status of a graphics file changes, I need to
> Angus> inform LyX. I do this with:
>
> Angus> LyXFunc::dispatch(LFUN_GRAPHICS_CHANGED_STATE,
On 20-Feb-2002 Jean-Marc Lasgouttes wrote:
> Why can't you signal the insets directly? It looks like a case where
> the lyxfunc think is really not appropriate... It looks like you could
> just call some InsetGraphics::fileChanged method directly.
You got a point there, but we have to provide a
On Wednesday 20 February 2002 1:32 pm, Angus Leeming wrote:
Actually, that was a bit premature. This doesn't work! Has anybody any idea
about how to write isStrPtr(str), strToPtr(str)? Should I use the C library
function strtoul?
Angus
> When the loading status of a graphics file changes, I n
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> When the loading status of a graphics file changes, I need to
Angus> inform LyX. I do this with:
Angus> LyXFunc::dispatch(LFUN_GRAPHICS_CHANGED_STATE, argument);
Angus> where argument is a list of insets as a space-separated stri
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 30-May-2001 Lars Gullik Bjønnes wrote:
| >
| > 2001-05-30 Juergen Vigna <[EMAIL PROTECTED]>
| > * boost/config.hpp: change include of to "LString.h".
| >
| > I am afraid we will see more and more of these changes to be able to
| > still
On 30-May-2001 Lars Gullik Bjønnes wrote:
>
> 2001-05-30 Juergen Vigna <[EMAIL PROTECTED]>
> * boost/config.hpp: change include of to "LString.h".
>
> I am afraid we will see more and more of these changes to be able to
> still use lyxstring. Hopefully there will not be enought of t
Svante Signell <[EMAIL PROTECTED]> writes:
| When compiling the latest cvs the include order of header files does
| not seem to be correct:
I belive this is a bogus report, note that you are using gcc 2.96
that is currently a _very_ experimental/unstable compiler.
Especially that the included-s
Hoorah! I have managed to compile the "rae" branch of CVS.
Many, many thanks to Jean-Marc for his suggestions about
integrating lyxstring with xtl, to Asger for passing my
problems with xtl to the xtl mailing list and to Jose
Orlando Pereira the xtl maintainer for his suggestions
about egcs.
Inci
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| I did not do it yet because I do not have much time now, but if Lars
| does not strongly objects, I think we should do that. It would also
| simplify a bit of the code with stringstreams.
Not true since other "objects" in the std::libs often use
Many thanks for the explanation, JMarc!
I conclude that egcs-1.1.2 causes code bloat and that its
STL is not standards compliant!
Onto your __STRING__ suggestion. I was trying to do
something like this last night, albeit in a much more
hacked way in order to resolve my problems in the rae
branch
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Reading the documentation in lyxstring.h: "it is written to be
Angus> a drop in replacement for STL string"
Angus> which suggests that the configure option
Angus> "--with-included-string" is just that --- an option. It is not,
Ang
On 19-Oct-99 Asger K. Alstrup Nielsen wrote:
>> shouln't return the above function and also find_first_of(...) an index
>> startin from 0 as all string functions do normally? I need a fast answer
>> as someone (I guess I know how ;) missinterpreted some function calls
>> in vspace.C and so they d
> shouln't return the above function and also find_first_of(...) an index
> startin from 0 as all string functions do normally? I need a fast answer
> as someone (I guess I know how ;) missinterpreted some function calls
> in vspace.C and so they don't work anymore. Now I would like to know
> if I
On Mon, 29 Mar 1999, Asger Alstrup Nielsen wrote:
> The Inset base class. Unfortunately, I'm not feeling too well at the
> moment (something with my throat), so I have not done my homework yet.
> Sorry to keep you waiting for my proposal.
Take your time. This is another very interesting part
On Mon, Mar 29, 1999 at 12:49:19PM +0200, Asger Alstrup Nielsen wrote:
> The Unicode.h file does not exist yet. Amir wrote an excellent script to
Actually, my script is just good. I think only Keanu Reeves writes
*excellent* scripts :)
> convert the unicode database to a C++ file, but the last
> If I understand you correctly, you want us to use "string" in all
> places where we today uses "LString". Is that correct? If so I think
> we should make the switch right away.
Yes, please go ahead and do that change. (This is irrespective of the current
discussion about whether InsetChunk sho
>> Lars Gullik Bjønnes writes:
LGB> glyphType() decomposeGlyph(); lowercase(); uppercase();
titlecase().
Lgb
49 matches
Mail list logo
