Re: [Lazarus] Multi-line msgid in PO file

2019-02-06 Thread Henry Vermaak via lazarus
On Wed, Feb 06, 2019 at 04:16:49PM +0300, Maxim Ganetsky via lazarus wrote: > 06.02.2019 15:42, Henry Vermaak via lazarus пишет: > > It's a pity we've missed the release, can you merge this onto > > fixes_2_0? > > I don't think that this is a good idea at this point of time, the > change is too

Re: [Lazarus] Multi-line msgid in PO file

2019-02-06 Thread Maxim Ganetsky via lazarus
06.02.2019 15:42, Henry Vermaak via lazarus пишет: > On Wed, Feb 06, 2019 at 03:58:37AM +0300, Maxim Ganetsky via lazarus wrote: >> 01.02.2019 19:38, Henry Vermaak пишет: >>> On Fri, 1 Feb 2019 at 12:46, Maxim Ganetsky via lazarus >>> wrote: As I remember, it was not the case earlier at

Re: [Lazarus] Multi-line msgid in PO file

2019-02-06 Thread Henry Vermaak via lazarus
On Wed, Feb 06, 2019 at 03:58:37AM +0300, Maxim Ganetsky via lazarus wrote: > 01.02.2019 19:38, Henry Vermaak пишет: > >On Fri, 1 Feb 2019 at 12:46, Maxim Ganetsky via lazarus > > wrote: > >>As I remember, it was not the case earlier at least with Poedit. But its > >>current version behaves

Re: [Lazarus] Multi-line msgid in PO file

2019-02-05 Thread Maxim Ganetsky via lazarus
01.02.2019 19:38, Henry Vermaak пишет: On Fri, 1 Feb 2019 at 12:46, Maxim Ganetsky via lazarus wrote: As I remember, it was not the case earlier at least with Poedit. But its current version behaves exactly as you describe. Maybe it is indeed a good idea to avoid changing these newlines. I

Re: [Lazarus] Multi-line msgid in PO file

2019-02-01 Thread Henry Vermaak via lazarus
On Fri, 1 Feb 2019 at 12:46, Maxim Ganetsky via lazarus wrote: > As I remember, it was not the case earlier at least with Poedit. But its > current version behaves exactly as you describe. Maybe it is indeed a > good idea to avoid changing these newlines. I will look into it. Thanks, much

Re: [Lazarus] Multi-line msgid in PO file

2019-02-01 Thread Maxim Ganetsky via lazarus
01.02.2019 12:43, Henry Vermaak пишет: > On Thu, 31 Jan 2019 at 23:38, Maxim Ganetsky via lazarus > wrote: >> Should be fixed in r60268. > > No, lazarus still adds an extra newline to the end of the msgid > entries in the PO files. This is incorrect, the original text does > not include a

Re: [Lazarus] Multi-line msgid in PO file

2019-02-01 Thread Henry Vermaak via lazarus
On Thu, 31 Jan 2019 at 23:38, Maxim Ganetsky via lazarus wrote: > 31.01.2019 14:01, Henry Vermaak via lazarus пишет: > > On Wed, Jan 30, 2019 at 08:19:47PM +0300, Maxim Ganetsky via lazarus wrote: > >> 30.01.2019 20:10, Henry Vermaak via lazarus пишет: > >>> I've had a problem with multi-line

Re: [Lazarus] Multi-line msgid in PO file

2019-01-31 Thread Maxim Ganetsky via lazarus
31.01.2019 14:01, Henry Vermaak via lazarus пишет: On Wed, Jan 30, 2019 at 08:19:47PM +0300, Maxim Ganetsky via lazarus wrote: 30.01.2019 20:10, Henry Vermaak via lazarus пишет: I've had a problem with multi-line translations not working and realised that an extra '\n' was appended to the last

Re: [Lazarus] Multi-line msgid in PO file

2019-01-31 Thread Henry Vermaak via lazarus
On Wed, Jan 30, 2019 at 08:19:47PM +0300, Maxim Ganetsky via lazarus wrote: > 30.01.2019 20:10, Henry Vermaak via lazarus пишет: > > I've had a problem with multi-line translations not working and realised > > that an extra '\n' was appended to the last line of the msgid in the PO > > file causing

Re: [Lazarus] Multi-line msgid in PO file

2019-01-30 Thread Maxim Ganetsky via lazarus
30.01.2019 20:10, Henry Vermaak via lazarus пишет: > I've had a problem with multi-line translations not working and realised > that an extra '\n' was appended to the last line of the msgid in the PO > file causing the translation lookup to fail. I'm assuming that this is > a bug, but thought

[Lazarus] Multi-line msgid in PO file

2019-01-30 Thread Henry Vermaak via lazarus
I've had a problem with multi-line translations not working and realised that an extra '\n' was appended to the last line of the msgid in the PO file causing the translation lookup to fail. I'm assuming that this is a bug, but thought I'd ask here first. I've attached a simple patch. Henry