Hello all!
KDevelop is currently bitten hard by a bug/limitation in desktoptojson. It
does not actually understand the .desktop files and custom properties get
converted to plain JSON strings. Looking at the sources it's also clear why,
only a selected list of .desktop properties is interpreted
On Sunday 16 November 2014 23:52:25 Milian Wolff wrote:
> Hello all!
>
> KDevelop is currently bitten hard by a bug/limitation in desktoptojson. It
> does not actually understand the .desktop files and custom properties get
> converted to plain JSON strings. Looking at the sources it's also clear
On Mon, Nov 17, 2014 at 12:24 AM, Milian Wolff wrote:
> On Sunday 16 November 2014 23:52:25 Milian Wolff wrote:
> > Hello all!
> >
> > KDevelop is currently bitten hard by a bug/limitation in desktoptojson.
> It
> > does not actually understand the .desktop files and custom properties get
> > con
On Monday, November 17, 2014 02:04:51 Aleix Pol wrote:
> On Mon, Nov 17, 2014 at 12:24 AM, Milian Wolff wrote:
> On Sunday 16 November 2014 23:52:25 Milian Wolff wrote:
> > KDevelop is currently bitten hard by a bug/limitation in desktoptojson. It
> > does not actually understand the .desktop fil
On Monday 17 November 2014 18:35:51 Sebastian Kügler wrote:
> On Monday, November 17, 2014 02:04:51 Aleix Pol wrote:
> > On Mon, Nov 17, 2014 at 12:24 AM, Milian Wolff wrote:
> > Fine, I could add similar code to desktoptojson, but:
> > > Since desktoptojson will be called for the plugins we sh
On Monday, November 17, 2014 18:50:04 Milian Wolff wrote:
> > > > Or can we nowadays write the .json files directly, i.e. can
> > > > scripty/ki18n
> > > > cope with them nowadays?
> > >
> > > So, any chance we can use .json directly here?
> >
> > That should be possible, you can just drop the json
On Tuesday 18 November 2014 12:48:42 Sebastian Kügler wrote:
> On Monday, November 17, 2014 18:50:04 Milian Wolff wrote:
> > > > > Or can we nowadays write the .json files directly, i.e. can
> > > > > scripty/ki18n
> > > > > cope with them nowadays?
> > > >
> > > > So, any chance we can use .json
El Dimarts, 18 de novembre de 2014, a les 14:09:00, Milian Wolff va escriure:
> On Tuesday 18 November 2014 12:48:42 Sebastian Kügler wrote:
> > On Monday, November 17, 2014 18:50:04 Milian Wolff wrote:
> > > > > > Or can we nowadays write the .json files directly, i.e. can
> > > > > > scripty/ki18
On Tuesday 18 November 2014 22:31:08 Albert Astals Cid wrote:
> El Dimarts, 18 de novembre de 2014, a les 14:09:00, Milian Wolff va
escriure:
> > On Tuesday 18 November 2014 12:48:42 Sebastian Kügler wrote:
> > > On Monday, November 17, 2014 18:50:04 Milian Wolff wrote:
> > > > > > > Or can we now
El Dimarts, 18 de novembre de 2014, a les 23:35:48, Milian Wolff va escriure:
> On Tuesday 18 November 2014 22:31:08 Albert Astals Cid wrote:
> > El Dimarts, 18 de novembre de 2014, a les 14:09:00, Milian Wolff va
>
> escriure:
> > > On Tuesday 18 November 2014 12:48:42 Sebastian Kügler wrote:
> >
On Tuesday 18 November 2014 23:45:56 Albert Astals Cid wrote:
> I didn't even know we were using json now. Why did we change from .desktop
> file to .json ones? What's the benefit? Seems like .desktop files did their
> job good enough and we have all the tooling available already.
Because that's w
El Dimarts, 18 de novembre de 2014, a les 23:01:14, Alex Merry va escriure:
> On Tuesday 18 November 2014 23:45:56 Albert Astals Cid wrote:
> > I didn't even know we were using json now. Why did we change from .desktop
> > file to .json ones? What's the benefit? Seems like .desktop files did
> > th
On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
> El Dimarts, 18 de novembre de 2014, a les 23:01:14, Alex Merry va escriure:
> > On Tuesday 18 November 2014 23:45:56 Albert Astals Cid wrote:
> > > I didn't even know we were using json now. Why did we change from
> > > .desktop
> >
Am Mittwoch, 19. November 2014, 01:28:51 schrieb Kevin Funk:
> On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
> > El Dimarts, 18 de novembre de 2014, a les 23:01:14, Alex Merry va
escriure:
> > > On Tuesday 18 November 2014 23:45:56 Albert Astals Cid wrote:
> > > > I didn't even k
On Wednesday 19 November 2014 17:30:28 Burkhard Lück wrote:
> Am Mittwoch, 19. November 2014, 01:28:51 schrieb Kevin Funk:
> > On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
> > > El Dimarts, 18 de novembre de 2014, a les 23:01:14, Alex Merry va
>
> escriure:
> > > > On Tuesday 18
El Dimecres, 19 de novembre de 2014, a les 18:46:28, Milian Wolff va escriure:
> On Wednesday 19 November 2014 17:30:28 Burkhard Lück wrote:
> > Am Mittwoch, 19. November 2014, 01:28:51 schrieb Kevin Funk:
> > > On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
> > > > El Dimarts, 18
Am Mittwoch, 19. November 2014, 18:46:28 schrieben Sie:
> So again, what is necessary to get this done?
First step is to make kdevelop in kf5 translatable using the "normal" po files,
then let's talk about json translation:
* KDevelop has 20 translation catalogs, but none of them is used (no
se
On Thu, Nov 20, 2014 at 8:47 AM, Burkhard Lück wrote:
> Am Mittwoch, 19. November 2014, 18:46:28 schrieben Sie:
> > So again, what is necessary to get this done?
>
> First step is to make kdevelop in kf5 translatable using the "normal" po
> files,
> then let's talk about json translation:
>
> * K
Am Mittwoch, 19. November 2014, 18:46:28 schrieben Sie:
> On Wednesday 19 November 2014 17:30:28 Burkhard Lück wrote:
> > Am Mittwoch, 19. November 2014, 01:28:51 schrieb Kevin Funk:
> > > On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
> > > > El Dimarts, 18 de novembre de 2014, a
Am Donnerstag, 20. November 2014, 10:36:20 schrieben Sie:
> On Thu, Nov 20, 2014 at 8:47 AM, Burkhard Lück wrote:
> > Am Mittwoch, 19. November 2014, 18:46:28 schrieben Sie:
> > > So again, what is necessary to get this done?
> >
> > First step is to make kdevelop in kf5 translatable using the "n
Am Mittwoch, 19. November 2014, 23:00:57 schrieb Albert Astals Cid:
>
> Well, there's two steps about this:
>
> 1) Know where the code is that gets the Name/Comment/Description from the
> json
>
> 2) Decide how you want to translate stuff (which may depend on 1)
>
> For 2) there's broadly two o
On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > 2.2 is easier (if possible to change the code in 1 to do it) since it does
> > not involve writing back strings to the json file.
>
> In kf5 using "LANGUAGE=foo kate" or LANGUAGE=foo kdevelop" (both projects
> do not install deskto
Am Donnerstag, 20. November 2014, 20:05:19 schrieb Sebastian Kügler:
> On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > > 2.2 is easier (if possible to change the code in 1 to do it) since it
> > > does
> > > not involve writing back strings to the json file.
> >
> > In kf5 using
El Dijous, 20 de novembre de 2014, a les 20:18:29, Burkhard Lück va escriure:
> Am Donnerstag, 20. November 2014, 20:05:19 schrieb Sebastian Kügler:
> > On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > > > 2.2 is easier (if possible to change the code in 1 to do it) since it
> > > >
Am Donnerstag, 20. November 2014, 22:55:03 schrieb Albert Astals Cid:
> El Dijous, 20 de novembre de 2014, a les 20:18:29, Burkhard Lück va
escriure:
> > Am Donnerstag, 20. November 2014, 20:05:19 schrieb Sebastian Kügler:
> > > On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > > >
2014-11-19 16:30 GMT+00:00 Burkhard Lück :
> Am Mittwoch, 19. November 2014, 01:28:51 schrieb Kevin Funk:
>> On Wednesday 19 November 2014 00:09:25 Albert Astals Cid wrote:
>> > El Dimarts, 18 de novembre de 2014, a les 23:01:14, Alex Merry va
> escriure:
>> > > On Tuesday 18 November 2014 23:45:56
On Wednesday, November 19, 2014 18:46:28 Milian Wolff wrote:
> > Looks to me like translations are not supported via json files.
>
> Please check the above. Anyhow, imo it should be our goal to get this
> supported. In the ideal scenario, a plugin would be just a .so installed
> into the right d
On Wednesday, November 19, 2014 23:00:57 Albert Astals Cid wrote:
> > So again, what is necessary to get this done?
>
> Well, there's two steps about this:
>
> 1) Know where the code is that gets the Name/Comment/Description from the
> json
I don't understand this. What do you mean exactly?
> 2
On Wednesday, November 19, 2014 18:46:28 Milian Wolff wrote:
> > Looks to me like translations are not supported via json files.
>
> Please check the above. Anyhow, imo it should be our goal to get this
> supported. In the ideal scenario, a plugin would be just a .so installed
> into the right d
On Wednesday, November 19, 2014 23:00:57 Albert Astals Cid wrote:
> > So again, what is necessary to get this done?
>
> Well, there's two steps about this:
>
> 1) Know where the code is that gets the Name/Comment/Description from the
> json
I don't understand this. What do you mean exactly?
> 2
El Dijous, 20 de novembre de 2014, a les 18:13:04, Sebastian Kügler va
escriure:
> On Wednesday, November 19, 2014 23:00:57 Albert Astals Cid wrote:
> > > So again, what is necessary to get this done?
> >
> > Well, there's two steps about this:
> >
> > 1) Know where the code is that gets the Nam
On Thursday 20 November 2014 19:57:54 Burkhard Lück wrote:
> Am Mittwoch, 19. November 2014, 23:00:57 schrieb Albert Astals Cid:
> > Well, there's two steps about this:
> >
> > 1) Know where the code is that gets the Name/Comment/Description from the
> > json
> >
> > 2) Decide how you want to tra
On Friday 21 November 2014 00:07:53 Milian Wolff wrote:
> On Thursday 20 November 2014 19:57:54 Burkhard Lück wrote:
> > Am Mittwoch, 19. November 2014, 23:00:57 schrieb Albert Astals Cid:
> > > Well, there's two steps about this:
> > >
> > > 1) Know where the code is that gets the Name/Comment/De
Am Freitag, 21. November 2014, 00:16:23 schrieben Sie:
> On Friday 21 November 2014 00:07:53 Milian Wolff wrote:
> > On Thursday 20 November 2014 19:57:54 Burkhard Lück wrote:
> > > Am Mittwoch, 19. November 2014, 23:00:57 schrieb Albert Astals Cid:
> > > > Well, there's two steps about this:
> > >
Am Freitag, 21. November 2014, 00:07:53 schrieb Milian Wolff:
> In general though, I'd say we should not blindly translate all *.json files
> in the repository. Rather, lets come up with a more specific extension
> filter. What about *.i18n.json? I fear that using *.json is too generic and
> will
On Thursday, November 20, 2014 20:18:29 Burkhard Lück wrote:
> Am Donnerstag, 20. November 2014, 20:05:19 schrieb Sebastian Kügler:
> > On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > > > 2.2 is easier (if possible to change the code in 1 to do it) since it
> > > > does
> > > > not
36 matches
Mail list logo
