After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732837 - Typos etc in translatable strings
Typos etc in translatable strings
Status: RESOLVED OBSOLETE
Product: gimp-gap
Classification: Other
Component: general
Current SVN
Other All
: Normal normal
: ---
Assigned To: hof
hof
Depends on:
Blocks:
 
 
Reported: 2014-07-07 12:39 UTC by Anders Jonsson
Modified: 2018-05-24 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix lots of typos. (34.79 KB, patch)
2015-08-05 20:04 UTC, Anders Jonsson
committed Details | Review
Followup typo fixes (2.83 KB, patch)
2015-08-05 20:29 UTC, Anders Jonsson
committed Details | Review
Followup typo fixes for docs/reference/txt (110.51 KB, patch)
2015-08-11 12:57 UTC, Anders Jonsson
committed Details | Review

Description Anders Jonsson 2014-07-07 12:39:44 UTC
First a big thanks for fixing all string issues I have reported so far.

I now looked through the 2-8 branch of gimp-gap, and there is still a few typos and other things that can be improved in the strings. No patch this time as I am not 100% certain of all of these.

Suggested changes below are all in translatable strings of gimp-gap:


gap/gap_blend_fill_main.c:                        , _("SVG file does not exist (use Save Pats button to create)."));


This should probably be "Save Paths"



gap/gap_colormask_dialog.c:                              _("DiffSensitvity:"), SCALE_WIDTH, 6,

"DiffSensitivity" unless the dropping of a letter is because of space constraints.



gap/gap_morph_dialog.c:                                         " when loacting corresponding coordinate"

Should probably be "locating"




gap/gap_morph_tween_dialog.c:                              _("Number of workpoints to be generated par processed frame"),

Should probably be "per processed frame"



gap/gap_split.c:                        "OFF: handle all layers and force visibiblity");

"visibility"



gap/gap_morph_tween_dialog.c:  label = gtk_label_new (_("Create Tweenfame(s):"));

Should probably be "Tweenframe(s)"





gap/gap_mpege.c:     argv[10].help_txt  = _("Search algorithmus used for P-frames");
gap/gap_mpege.c:     argv[11].help_txt  = _("Search algorithmus used for B-frames");

algorithmus is german. Shold be "algorithm", or possibly "algorithms" if it is plural.





gap/gap_story_render_processor.c:    p_set_stb_error(sterr, _("No Frames or Images found ...."));

An ellipsis usually only contains three periods... 




gap/gap_morph_tween_dialog.c:                                "value 0 turns off intensity desceding deformation, "


desceding is not an existing word, this should possibly be "descending"






gap_story_properties.c
  filesel = gtk_file_selection_new ( _("Set Colormark Parmeter Filename"));
  pw->pw_colormask_file_filesel = filesel;

Here I suspect two typos, since I see variable names about Colormask. If that is the case "Colormark Parmeter" should really be "Colormask Parameter" here.



gap/gap_video_index_creator.c:                                              " based on a few quick timcode probereads.\n"

This could possibly be "timecode", but I am not certain as I see timcode is used in some variable names as well, although not as much as timecode is used.



gap/gap_water_pattern.c:  gimp_help_set_help_data (checkbutton, _("ON: create waterpattern cloud layers according options. OFF: Use external pattern layers. "), NULL);

Should probably be "according to options" to be grammatically correct.





gap/gap_decode_mplayer.c-  argv[ii].help_txt  = _("optimization factor"
gap/gap_decode_mplayer.c:                        "(is ignored when other formats are used)");
--
gap/gap_decode_mplayer.c-  argv[ii].help_txt  = _("Smooth factor"
gap/gap_decode_mplayer.c:                        "(is ignored when other formats are used)");
--
gap/gap_decode_mplayer.c-  argv[ii].help_txt  = _("Enable progressive jpeg encoding"
gap/gap_decode_mplayer.c:                        "(is ignored when other formats are used)");
--
gap/gap_decode_mplayer.c-  argv[ii].help_txt  = _("Enable baseline jpeg encoding"
gap/gap_decode_mplayer.c:                        "(is ignored when other formats are used)");
--

In these strings there is no space in front of the bracket.
In other words end the preceding line with a space:
"optimization factor "
"Smooth factor "
"Enable progressive jpeg encoding "
"Enable baseline jpeg encoding "

in the strings above





../gap/gap_detail_align_exec.c:1279
This filter requires a current path with 4 points,where point 1 and 2 mark "

This should have a space after the comma, so "points, where"


gap/gap_onion_dialog.c:                         , _("Descending opacity for 2.nd onionskin layer")


"2.nd" is usually written "2nd"




vid_enc_ffmpeg/gap_enc_ffmpeg_gui.c:2477:
 _("Bypass the FFMPEG Vidoencoder where inputframes can "
                            "be copied 1:1 from an input MPEG videofile."
                            "This experimental feature provides lossless MPEG "
                            "video cut, but works only for the MPEG Fileformats.")

gap/gap_story_dialog.c:
  argv[l_ii].help_txt  = _("Select preferred video decoder library, "
                       "or leave empty for automatic selection."
                       "The decoder setting is only relevant if "

gap/gap_range_ops.c-  argv[5].help_txt  = _("Convert to another imagetype, or keep imagetype as it is. "
                        "Most fileformats can't handle all types and may require a conversion."
                        "Example: GIF can not handle RGB and requires convert to indexed imagetype.");


Here there is no space between sentences, this can be fixed by ending the lines with "input MPEG videofile. ", "for automatic selection. " and "may require a conversion. " respectively.






vid_enc_ffmpeg/gap_enc_ffmpeg_gui.c:2477:
  gimp_help_set_help_data (checkbutton
                        , _("Bypass the FFMPEG Vidoencoder where inputframes can "

Should be "Videoencoder"



vid_enc_ffmpeg/gap_enc_ffmpeg_gui.c:  
_("Recommanded Framesize")
vid_enc_ffmpeg/gap_enc_ffmpeg_gui.c:  
_("Recommanded Framesize")

vid_enc_ffmpeg/gap_enc_ffmpeg_gui.c:
       detailInfo = g_strdup_printf(_("Selected Fileformat : [%s] %s\n"
                                  "Recommanded Video CODEC : %s\n"
                                  "Recommanded Audio CODEC : %s\n"
                                  "Extension(s): %s %s"

"recommanded" should be "recommended" in all these.







gap/gap_video_index_creator.c
"Conditional video index creation, "
                                              " based on a few quick timcode probereads.\n"
                                              "Skip index creation if native seek seems possible\n"
                                              "\nWARNING: positioning via native seek may not work exact in case critical "
                                              "timecode steps were not detected in the quick test)"


This string only has an ending parenthesis, and ")" should either be deleted, or a "(" added somewhere.





gap/gap_range_ops.c:                        "regardless to the other settings of layer selection.");

Here it would be better to use "of" instead of "to" after regardless. 
https://en.wiktionary.org/wiki/regardless_of




gap/gap_fg_matting_dialog.c:                         " GRAY pixels (value 1 upto 240) are marked as Undefined "

gap/gap_story_file.c:       _("illegal number: %s (valid range is %.3f upto %.3f)"
gap/gap_story_file.c:        _("illegal number: %s (valid range is %d upto %d)\n"


"up to" is most usually written as two words.




Regards,
Anders Jonsson
Comment 1 Anders Jonsson 2015-08-05 20:04:17 UTC
Created attachment 308814 [details] [review]
Fix lots of typos.

This fixes most of the strings mentioned in the report along with some other spelling issues. The patch is against gimp-gap-2-8 branch.


Left are the words where I was uncertain what would be best:
algorithmus
desceding
DiffSensitvity
timcode
Comment 2 Anders Jonsson 2015-08-05 20:29:45 UTC
Created attachment 308816 [details] [review]
Followup typo fixes

Found some more string typos while testing previous patch. This much smaller patch applies on the earlier one.
Comment 3 Anders Jonsson 2015-08-11 12:57:05 UTC
Created attachment 309063 [details] [review]
Followup typo fixes for docs/reference/txt

I had a closer look at the .txt files under docs/reference/txt, and created a patch for typos in that folder. This applies on top of the previous two patches attached to this bug report.
Comment 4 Anders Jonsson 2015-08-31 18:07:05 UTC
Thank you Wolfgang for applying patches as well as other fixes for this bug. It looks great.

Now it's just one more patch from the report to be considered for inclusion: https://bugzilla.gnome.org/attachment.cgi?id=309063&action=diff

It's a larger patch than the other ones, but it is just typo fixes in plain text files, so I don't think there should be anything controversial there.
Comment 5 André Klapper 2017-08-01 11:16:11 UTC
Comment on attachment 309063 [details] [review]
Followup typo fixes for docs/reference/txt

I went through the last patch and as it's language/typo fixes 'only' (thanks for finding and correcting all these, Anders!), I took the liberty to merge the patch (though not being a gimp-gap maintainer) in git commit 1725bb5.
Comment 6 André Klapper 2017-08-01 11:16:34 UTC
Probably "overwriting wht was" and "with this plug-ins" and "and can NOT be specified explicite" and "(usual 2 for stereo)" and "will not play synchron !" and "cload1 and cloud2" also welcome fixes, hence leaving this ticket open.
Comment 7 GNOME Infrastructure Team 2018-05-24 10:24:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp-gap/issues/20.