Add context support for editor property name i18n

[timothyqiu]

Fixes #82788

• Two optional params are added to process_name(): full property path & class name
  • Full property path is enough for most use cases, e.g. constant_force vs force/8_bit
  • Class name is used when full property paths are the same, but have different meanings, e.g. Normal in Decal.texture_normal and TextureButton.texture_normal
• Context is assigned inside EditorPropertyNameProcessor
  • Context is rarely needed.
  • Easy to parse when extracting for POT.
• Context can be specified either for full/property/path or for Class::full/property/path
  • Class name is rarely needed. I think this kind of properties should be renamed when possible.
  • Simplifies theme_overrides_style/normal as it applies to many UI nodes

[Wuzzy2]

Using "Noun" or "Verb" as context is a bad idea because sometimes even identical nouns or verbs can have different meanings.

The Gettext context entry is supposed to describe something like a topic or category that fits to that string or some other identifier that clearly helps to fix the ambiguity.

See also: https://www.gnu.org/software/gettext/manual/gettext.html#Contexts

[AThousandShips]

Using "Noun" or "Verb" as context is a bad idea because sometimes even identical nouns or verbs can have different meanings.

Granted but it refers to how English uses it, i.e. what word to translate from

The difference between "A Constant Force" and "To Be Constant Forcing"

[timothyqiu]

Using "Noun" or "Verb" as context is a bad idea because sometimes even identical nouns or verbs can have different meanings.

I think you might be worried that "Noun" and "Verb" won't resolve all the possible ambiguities in the project? These contexts are not part of a fixed set of labels that would be picked from when a new ambiguous string appears. They are chosen on a case-by-case basis for each ambiguous string independently.

In this case, the two existing usages are "Constant Force Applied to the Object" and "Force the Audio File to be Imported as 8-Bit". I thought about "Physics" vs "Audio" too, but it feels weird because the word "force" itself has nothing to do with audio.

[Wuzzy2]

Yes, technically the context could be anything to just resolve the collision. I was just arguing it could be a little bit more descriptive. But technically this is not 100% required as long all collisions are resolved.

[timothyqiu]

@Wuzzy2 Any suggestions?

[Wuzzy2]

For the physical "Force", name the context "physics".
For the concept of forcing a setting, name the context "forcing a setting".

[timothyqiu]

Changed to "Physics" and "Enforce". I think "forcing a setting" is a bit specific.

[KoBeWi]

I tested the context for Normal and it works for "Geometry", but not for "Ordinary". Theme overrides translate the names without using context.

[timothyqiu]

Good catch! I tested with Ordinary one and no context one being the same, so I didn't spot that bug. I'll work on that.

[timothyqiu]

Note: These two are removed because

• They were used to store default theme fonts when Godot was open sourced. But fonts were changed to a dedicated theme member later, so these entries were abandoned.
• They add unnecessary strings to translate. Not worth adding exceptions for.

[akien-mga]

Thanks!