dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
42,954 Commits 321 Branches 272 Tags 778 MiB
Commit Graph

4365 Commits

Author SHA1 Message Date
Ryuta Fujii 975d93758a Update Japanese translation 2019-02-15 14:12:16 +00:00
Piotr Drąg 51d6b617e6 Update Polish translation 2019-02-14 19:49:00 +01:00
Rodrigo Lledó 8b709279e1 Update Spanish translation 
(cherry picked from commit daf7754e7a)
 2019-02-14 12:18:18 +00:00
Ryuta Fujii dbca709fe8 Update Japanese translation 2019-02-13 14:12:12 +00:00
Ryuta Fujii a5a62fdf02 Update Japanese translation 2019-02-12 14:30:52 +00:00
Piotr Drąg 036f6e42c4 Update Polish translation 2019-02-11 20:27:57 +01:00
Michael Natterer 410ffc435e app: move file-pat-load from the file-pat plug-in to the core 2019-02-11 18:35:07 +01:00
Michael Natterer a4e77e57f6 app, plug-ins: start consolidating brush and pattern loading/saving code 
We currently have brush and pattern I/O code in both the core and
plug-ins. This commit starts removing plug-in code in favor of having
one copy of the code in the core, much like XCF loading and saving is
implemented.

Add app/file-data/ module with file procedure registering code, for
now just with an implementation of file-gbr-load.

Remove the file-gbr-load code from the file-gbr plug-in.
 2019-02-11 12:51:31 +01:00
Rodrigo Lledó af77be64f9 Update Spanish translation 
(cherry picked from commit dfe1dbe0ad)
 2019-02-11 07:49:40 +00:00
Ryuta Fujii 1ad2fcdb5e Update Japanese translation 2019-02-10 15:45:21 +00:00
Ryuta Fujii d634860940 Update Japanese translation 2019-02-09 13:02:27 +00:00
Piotr Drąg a1538c2010 Update Polish translation 2019-02-08 20:36:46 +01:00
Jehan cb025cec64 Issue #2922: fix msgctxt s/view-action/view-zoom-action/ for 5 strings. 
Similar to the previous fix in commit 7a5e5be35e, this doesn't change
anything in the actual string and its usage within the software. Thus
following yesterday's discussion on gnome-i18n ML, I just do the
search-and-replace fix.

This is complementary to commit 6c5b6c6135, which fixed the code where a
same GimpEnumActionEntry was mixing translatable strings with various
contexts.
 2019-02-08 12:57:59 +01:00
Jehan 7a5e5be35e po: fix the context (msgctx) for 2 strings. 
See commit f8f3a74971.
The context change was basically a bug fix, and nothing changed in the
original string, nor its actual GUI context/usage. Therefore there is no
need to invalidate the translations (mark it "fuzzy", which would be
what would happen automatically after this change) for the 43 languages
which already translated these. Let's just search-and-replace all the po
files with the correct context.

For the record, I got the green light from several translators on
gnome-i18n ML so let's fix. :-)
 2019-02-07 18:29:21 +01:00
Ryuta Fujii f85870ca13 Update Japanese translation 2019-02-06 13:36:34 +00:00
Ryuta Fujii 50b93d2034 Update Japanese translation 2019-02-06 13:08:23 +00:00
Ryuta Fujii 2ea2e84f0f Update Japanese translation 2019-01-31 16:07:48 +00:00
Ryuta Fujii 8cfdf13af0 Update Japanese translation 2019-01-30 14:28:24 +00:00
Daniel Mustieles 08d75d795e Update Spanish translation 2019-01-30 07:48:05 +00:00
Ryuta Fujii 78dd964000 Update Japanese translation 2019-01-28 17:26:44 +00:00
Ryuta Fujii abecf6c845 Update Japanese translation 2019-01-27 15:24:34 +00:00
Balázs Meskó 8f0ed2422f Update Hungarian translation 
(cherry picked from commit 316c47da6f)
 2019-01-26 21:38:16 +00:00
Ryuta Fujii a776232e14 Update Japanese translation 2019-01-26 16:16:45 +00:00
Piotr Drąg 586107ccbb Update Polish translation 2019-01-26 11:25:24 +01:00
Ryuta Fujii 3274d86e79 Update Japanese translation 2019-01-23 17:04:45 +00:00
Ryuta Fujii f3ed7d4b43 Update Japanese translation 2019-01-22 12:48:02 +00:00
Alan Mortensen 3dd66e14b1 Updated Danish translation 2019-01-21 14:06:50 +01:00
Ryuta Fujii 02d6478c24 Update Japanese translation 2019-01-18 22:47:10 +00:00
Piotr Drąg dec747a515 Update Polish translation 2019-01-17 11:50:02 +01:00
Ryuta Fujii c44f94f368 Update Japanese translation 2019-01-15 16:26:49 +00:00
Ryuta Fujii 41d5986a2b Update Japanese translation 2019-01-14 16:45:54 +00:00
Piotr Drąg 250b9c033e Update Polish translation 2019-01-13 12:36:16 +01:00
Piotr Drąg ee646716f4 Update Polish translation 2019-01-12 13:13:16 +01:00
Ryuta Fujii f3972329e3 Update Japanese translation 2019-01-10 17:27:45 +00:00
Ryuta Fujii 50696780fe Update Japanese translation 2019-01-10 17:17:59 +00:00
Ryuta Fujii a67ccc63f7 Update Japanese translation 2019-01-10 13:53:17 +00:00
Piotr Drąg aaf8b8b53c Update POTFILES.in 2019-01-09 19:53:10 +01:00
Ryuta Fujii 25cf13402c Update Japanese translation 
(cherry picked from commit 0a22773a17)
 2019-01-09 13:13:02 +00:00
Ryuta Fujii 5f176172e6 Update Japanese translation 
(cherry picked from commit 51ecd3e14e)
 2019-01-09 13:06:52 +00:00
Ryuta Fujii 4c13eee294 Update Japanese translation 
(cherry picked from commit b7793b9c21)
 2019-01-08 15:27:16 +00:00
Piotr Drąg 879ad52477 Update Polish translation 2019-01-06 19:21:49 +01:00
Ryuta Fujii 7435be68cc Update Japanese translation 
(cherry picked from commit 73597b4efd)
 2019-01-04 21:32:25 +00:00
Michael Natterer 39406b83d3 Issue #2136 - On-image UI for adjusting Linear Motion Blur 
Add on-canvas GUI (simple lines) for circular, linear and zoom motion
blur. The restrictions in the interaction show pretty well that there
is room for improvement here, the line is just a bit too generic, but
it's better than nothing.
 2019-01-04 14:38:49 +01:00
Ell ed7ea51fb7 app: remove "Edit -> Fade..." 
This commit completely removes the "Edit -> Fade..." feature,
because...

- The main reason is that "fade" requires us to keep two buffers,
  instead of one, for each fadeable undo step, doubling (or worse,
  since the extra buffer might have higher precision than the
  drawable) the space consumed by these steps.  This has notable
  impact when editing large images.  This overhead is incurred even
  when not actually using "fade", and since it seems to be very
  rarely used, this is too wasteful.

- "Fade" is broken in 2.10: when comitting a filter, we copy the
  cached parts of the result into the apply buffer.  However, the
  result cache sits after the mode node, while the apply buffer
  should contain the result of the filter *before* the mode node,
  which can lead to wrong results in the general case.

- The same behavior can be trivially achieved "manually", by
  duplicating the layer, editing the duplicate, and changing its
  opacity/mode.

- If we really want this feature, now that most filters are GEGL
  ops, it makes more sense to just add opacity/mode options to the
  filter tool, instead of having this be a separate step.
 2018-12-27 11:44:25 -05:00
Piotr Drąg 10cdef9af1 Update Polish translation 2018-12-24 14:42:38 +01:00
Piotr Drąg cbee0ed5a3 Update Polish translation 2018-12-23 13:53:27 +01:00
Piotr Drąg 079c70cc0b Update Polish translation 2018-12-16 12:13:49 +01:00
Ask Hjorth Larsen e4e4422f5c revert last commit of Danish translation -- file incomplete 2018-12-12 21:18:48 +01:00
Alan Mortensen 15049da94e Updated Danish translation 2018-12-12 21:14:37 +01:00
Piotr Drąg d90b0024f0 Update Polish translation 2018-12-09 12:23:29 +01:00