Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#21865 closed enhancement (fixed)

[WIP patch] Harmonize menu strings style

Reported by: gaben Owned by: gaben
Priority: minor Milestone: 22.03
Component: Core Version:
Keywords: string Cc:

Description

The strings in the settings consist of multiple styles:

  • Capital first letter, rest normal
  • Capital first letter, rest normal and dot at the end.
  • Capital Some letter, no dot at the end
  • Capital Some letter, dot at the end.

In the provided patch I tried to harmonize these. Unfortunately, it affects the translations as well, but they are ugly.

Attachments (1)

harmonize_strings.patch (39.1 KB ) - added by gaben 3 years ago.

Download all attachments as: .zip

Change History (8)

by gaben, 3 years ago

Attachment: harmonize_strings.patch added

comment:1 by stoecker, 3 years ago

Dropping the icon comments breaks things.

Also removing the dots in the tooltips is not useful or sensible. The tool tips are sentences and thus also should have a dot. And that change would waste a lot of translation effort for nearly nothing.

Please fix these two then we can look at the remaining ones.

in reply to:  1 comment:2 by taylor.smock, 3 years ago

Owner: changed from team to gaben
Status: newneedinfo
Summary: [patch] Harmonize menu strings style[WIP patch] Harmonize menu strings style

@gaben: Just so you know, one of the things it breaks is source:trunk/scripts/geticons.pl.

Anyway, are you going to update the patch with @stoecker's feedback, or is this ticket dead?

comment:3 by gaben, 3 years ago

Thanks, at least I know what I broke. Interestingly I found classes without these comment like "hooks", so I thought they are not essential. Also without them, IntelliJ's inline parameter hinting works, which is more important without knowing their real purpose.

I would say half dead. The ticket is about harmonisation. If you think "The tool tips are sentences and thus also should have a dot", I would add dots to tooltips, which will also ruin translations. I get it and agree, but this way strings will never improve.

Last edited 3 years ago by gaben (previous) (diff)

comment:4 by taylor.smock, 3 years ago

There are some things I think we could safely apply from your patch. Example: Hightlight -> Highlight.

But for the mass changes add ., I'd be happier if there was some way to link the previous translation, possibly marking it as dirty or something.

It looks like gettext has a fuzzy attribute, and I'd really want to have it set for most of the changes. But I also don't know how fuzzy works with our current system, or if we even set it anywhere.

comment:5 by stoecker, 3 years ago

Resolution: fixed
Status: needinfoclosed

In 18416/josm:

text fix, fix #21865

comment:6 by stoecker, 3 years ago

In 18417/josm:

text fix, fix #21865

comment:7 by stoecker, 3 years ago

Milestone: 22.03

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain gaben.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.