On Tue, May 10, 2016 at 01:28:09AM -0400, Scott Kostyshak wrote:
> On Tue, May 10, 2016 at 07:22:14AM +0200, Georg Baum wrote:
> > Uwe Stöhr wrote:
> >
> > > Am 07.05.2016 um 14:34 schrieb Uwe Stöhr:
> > >
> > >> Many thanks. I tested it and it works well.
> > >> +1 to go in to master.
> > >>
> >
On Tue, May 10, 2016 at 07:22:14AM +0200, Georg Baum wrote:
> Uwe Stöhr wrote:
>
> > Am 07.05.2016 um 14:34 schrieb Uwe Stöhr:
> >
> >> Many thanks. I tested it and it works well.
> >> +1 to go in to master.
> >>
> >>> Imagemagick is unfortunately known for frequent security issues. IMHO
> >>> th
Uwe Stöhr wrote:
> Am 07.05.2016 um 14:34 schrieb Uwe Stöhr:
>
>> Many thanks. I tested it and it works well.
>> +1 to go in to master.
>>
>>> Imagemagick is unfortunately known for frequent security issues. IMHO
>>> the fix would be safe for 2.2.0,
>>
>> +1
>
> Scott, this issue is important fo
Am 10.05.2016 um 01:50 schrieb Uwe Stöhr:
Am 09.05.2016 um 21:48 schrieb Georg Baum:
Therefore I asked. How do they get the .po files after a string remerge?
I don't know. Maybe from git but I know also that download them via
our TRAC websites. If it is the latter I fear they will get their
On Tue, May 10, 2016 at 07:09:04AM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
> >>
> >> Done. Now I would recommend to merge all .po file contributions that are
> >> not based on the latest remerge by
> >>
> >> python devel
Scott Kostyshak wrote:
> On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
>>
>> Done. Now I would recommend to merge all .po file contributions that are
>> not based on the latest remerge by
>>
>> python development/tools/mergepo.py -o -l xx -t po /tmp/
>>
>> wher xx is the language
On Mon, May 09, 2016 at 09:51:45PM +0200, Georg Baum wrote:
> José Matos wrote:
>
> > On Thursday, May 5, 2016 2:19:32 PM WEST Georg Baum wrote:
> >> The former is safe and easy (see attached). I am not familiar enough with
> >> python3 to judge whether TeXFiles.py can be made work with python3 an
Kornel Benko wrote:
> Ah, yes. I remember trying many things to convince 'make' to be as lazy as
> possible. Changing some source does not always affect the translatable
> strings. So we may also stay with your suggestion. In the end, it does not
> take that long.
OK, I did that for consistency r
On Mon, May 09, 2016 at 07:58:53PM -0400, Ian Wilder wrote:
> +1 for not branching. If it's just print statements, the use functions to be
> compatible with Python 3.
> A lot of Python 3 functionality has been backported to 2.x
Thanks for the interest, Josh and Ian. Note that we have a ticket wher
On Sun, May 08, 2016 at 10:33:23PM +0100, Guillaume Munch wrote:
> Le 06/05/2016 21:09, Scott Kostyshak a écrit :
> > On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> > > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> > > > What am I missing?
> > > >
> > >
> > > #10068: Files
On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > On Thu, May 05, 2016 at 02:32:46PM +0200, Georg Baum wrote:
> >>
> >> I would like to merge all changes to mergepo.py from 2.3-staging to
> >> master (see attached). The users won't see this script at all,
On Mon, May 09, 2016 at 05:25:40PM +0100, José Matos wrote:
> On Saturday, May 7, 2016 11:39:32 AM WEST Georg Baum wrote:
> > I am unsure about building LyX where "python" is python 3. We fixed some
> > build scripts to work both with python 2 and 3, but maybe there are others
> > that don't work
On Mon, May 09, 2016 at 12:03:20PM +0200, Helge Hafting wrote:
>
>
> Den 07. mai 2016 08:35, skrev Guenter Milde:
> > This leaves open the possibility to (re)activate the validator in 2.2.1
> > after a non-rushed discussion.
> >
> > I still favour allowing values that
> > * LaTeX allows,
> >
On Sat, May 07, 2016 at 11:59:14AM +0200, Georg Baum wrote:
> > I guess checking problems on other PCs would be helpful. Unfortunately,
> > I don't have a second PC on which this is easily done. On the other
> > hand, while it might be a nice information to have, I don't think that
> > this should
On Fri, May 06, 2016 at 11:17:08PM +0200, Stephan Witt wrote:
>
> > Am 06.05.2016 um 21:07 schrieb Scott Kostyshak :
> >
> > On Thu, May 05, 2016 at 10:55:53PM +0200, Stephan Witt wrote:
> >> Am 05.05.2016 um 13:49 schrieb Jean-Marc Lasgouttes :
> >>>
> >>> Le 04/05/16 à 22:12, Scott Kostyshak a
+1 for not branching. If it's just print statements, the use functions
to be compatible with Python 3.
A lot of Python 3 functionality has been backported to 2.x
On 2016-05-09 00:35:57 +, Josh Hieronymus said:
Looking over the code, it looks like much of the problem is that Python
2 has pr
Am 09.05.2016 um 21:48 schrieb Georg Baum:
I think it is more important to please the translators.
Therefore I asked. How do they get the .po files after a string remerge?
I don't know. Maybe from git but I know also that download them via our
TRAC websites. If it is the latter I fear they
Am 07.05.2016 um 14:34 schrieb Uwe Stöhr:
Many thanks. I tested it and it works well.
+1 to go in to master.
Imagemagick is unfortunately known for frequent security issues. IMHO the
fix would be safe for 2.2.0,
+1
Scott, this issue is important for Windows users. Can this please go in
be
Am Montag, 9. Mai 2016 um 21:59:05, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Looks good. But you could omit the creation of ${_lyxname}.cat_tmp.pot, as
> > this was only needed to make the conversion.
> >
> > So
> > COMMAND ${LYX_PYTHON_EXECUTABLE}
> > ARGS "${TOP_CMAKE_PATH}/po/cat
Am 09.05.2016 um 22:28 schrieb Guillaume Munch :
>
> Le 09/05/2016 21:14, Georg Baum a écrit :
>> This is BTW a good example why it is always useful to look at the diff
>> before committing, and why having redable diffs (as currently discussed in
>> the .po file thread) is important.
>>
>
> Coul
Guillaume Munch wrote:
> Le 09/05/2016 21:14, Georg Baum a écrit :
>> This is BTW a good example why it is always useful to look at the diff
>> before committing, and why having redable diffs (as currently discussed
>> in the .po file thread) is important.
>>
>
> Could the same not be said for sv
Le 09/05/2016 21:14, Georg Baum a écrit :
This is BTW a good example why it is always useful to look at the diff
before committing, and why having redable diffs (as currently discussed in
the .po file thread) is important.
Could the same not be said for svgz and sfd files? In particular it
wou
Guillaume Munch wrote:
> I think compression has been enabled by mistake.
It also made git think the file is binary, therefore not applying the native
line end conversion after the fix anymore. I fixed this at 38e9752c01. From
now on, everything should be fine again.
This is BTW a good example
Kornel Benko wrote:
> Looks good. But you could omit the creation of ${_lyxname}.cat_tmp.pot, as
> this was only needed to make the conversion.
>
> So
> COMMAND ${LYX_PYTHON_EXECUTABLE}
> ARGS "${TOP_CMAKE_PATH}/po/cat.py" ${_py_sources} >
> "${CMAKE_CURRENT_BINARY_DIR}/${_lyxname}.cat.
José Matos wrote:
> On Thursday, May 5, 2016 2:19:32 PM WEST Georg Baum wrote:
>> The former is safe and easy (see attached). I am not familiar enough with
>> python3 to judge whether TeXFiles.py can be made work with python3 and
>> python2 safely.
>>
>> Georg
>
> As Georg says the patch is safe
Am 09.05.2016 um 01:34 schrieb Uwe Stöhr:
Am 08.05.2016 um 22:36 schrieb Georg Baum:
3) A translator sends a .po file with unix line ends
4) A translator sends a .po file with windows line ends
The question is how can I check this?
You don't need to check that, but if you want, open the fi
On Wednesday, April 6, 2016 5:48:20 AM WEST Enrico Forestieri wrote:
> Done at d4ca8d74.
Thank you Enrico. :-)
--
José Abílio
On Tuesday, April 12, 2016 9:31:34 PM WEST Jean-Marc Lasgouttes wrote:
> Le 09/04/16 09:48, Scott Kostyshak a écrit :
> > I'm planning to follow standard practice of specifying the number of
> > minor versions of 2.1 to 5, as below.
>
> What is this used for?
>
> JMarc
It should be used for lyx2
On Saturday, May 7, 2016 11:39:32 AM WEST Georg Baum wrote:
> I am unsure about building LyX where "python" is python 3. We fixed some
> build scripts to work both with python 2 and 3, but maybe there are others
> that don't work with python 3 yet. Assuming that Helge confirms the fix for
> conf
Le 09/05/2016 06:21, Pavel Sanda a écrit :
I agree. If you ever find time to look at the issue that would earn you beer
delivery in front of your door :)
I have now bookmarked this thread in case I need to refer to it later :)
Am 09.05.2016 um 15:14 schrieb Helge Hafting :
>
> Den 09. mai 2016 12:33, skrev Stephan Witt:
>> Am 09.05.2016 um 11:39 schrieb Helge Hafting :
>>> Also, the spell checker work if I set the preference to 'Aspell' or
>>> 'Enchant'. Using 'Hunspell',
>>> I still get 'The spell checker has no dicti
Den 09. mai 2016 12:33, skrev Stephan Witt:
Am 09.05.2016 um 11:39 schrieb Helge Hafting :
Also, the spell checker work if I set the preference to 'Aspell' or 'Enchant'.
Using 'Hunspell',
I still get 'The spell checker has no dictionaries', but one working
spellchecker is enough for me.
Wer
On Thursday, May 5, 2016 2:19:32 PM WEST Georg Baum wrote:
> The former is safe and easy (see attached). I am not familiar enough with
> python3 to judge whether TeXFiles.py can be made work with python3 and
> python2 safely.
>
> Georg
As Georg says the patch is safe for both python 2 and 3.
I
On 07.05.16 20:20, Guenter Milde wrote:
> On 2016-05-07, mn wrote:
>> On 06.05.16 21:11, Guenter Milde wrote:
>>> Actually, here I get with German keyboard and English locale:
>>> For single quotes you have to use the shortcut Alt+".
>
>> For English doc/UserGuide.lyx.
>
>> [Since I prefer direc
Am 09.05.2016 um 11:39 schrieb Helge Hafting :
>
>
>
> Den 05. mai 2016 14:19, skrev Georg Baum:
>> The former is safe and easy (see attached). I am not familiar enough with
>> python3 to judge whether TeXFiles.py can be made work with python3 and
>> python2 safely.
>>
> This patch improves 2.2
Den 07. mai 2016 08:35, skrev Guenter Milde:
This leaves open the possibility to (re)activate the validator in 2.2.1
after a non-rushed discussion.
I still favour allowing values that
* LaTeX allows,
* have use cases (maybe rare) and
* are not "dangerous".
Negative margins has some u
Den 05. mai 2016 14:19, skrev Georg Baum:
The former is safe and easy (see attached). I am not familiar enough with
python3 to judge whether TeXFiles.py can be made work with python3 and
python2 safely.
This patch improves 2.2.0-rc1. Output from configure is now:
...
+Indexing TeX files...
In
Am Montag, 9. Mai 2016 um 11:11:17, schrieb Helge Hafting
>
> Den 04. mai 2016 19:54, skrev Scott Kostyshak:
> > On Wed, May 04, 2016 at 06:55:06PM +0200, Helge Hafting wrote:
> >>
> >> Den 04. mai 2016 18:42, skrev Helge Hafting:
> >>> I am not sure if this has any ill effects, but it doesn't l
Den 04. mai 2016 19:54, skrev Scott Kostyshak:
On Wed, May 04, 2016 at 06:55:06PM +0200, Helge Hafting wrote:
Den 04. mai 2016 18:42, skrev Helge Hafting:
I am not sure if this has any ill effects, but it doesn't look good.
Actually, I found this after noticing that spell checking does not
39 matches
Mail list logo
