Modify

Opened 2 months ago

Closed 2 months ago

Last modified 13 days ago

#17380 closed enhancement (fixed)

Add translation en_CA

Reported by: Hb--- Owned by: team
Priority: normal Milestone: 19.02
Component: Core Version:
Keywords: i18n english canada Cc:

Description (last modified by Hb---)

Please enable en_CA to be delivered with JOSM. All strings are translated as of today.

The Canadian translation is only a dialect. It wants to deliver a terminology as distinguishable as possible. It prefers to:

  1. Bind a verb exclusively to a noun or an action.
    • While the source uses "to select" for objects, menu items, list entries, files, checkbox states, download areas and nearly everything else the dialect tries to bind this verb to the meaning of
      selecting map objects for the Selection.
      The dialect
      chooses menu items, list entries, data sets and files
      checks checkbox states and
      defines download areas.
      Additionally the dialect goes even further and often replaces the term the selected objects by the proper noun the Selection. With this noun the Canadians want to honor the superior importance of these hand-picked elements in JOSM.

    • The source uses "to move" for objects, tags and for the map view but the dialect limits this to
      to moves objects only and
      pans the map and
      shifts tags from ways to relation for example.

    • The source uses "to toggle" for dialog panels, some states of the GUI and map data. But the dialect limits this to toggled by TAB keystroke effects and uses hide/show for other means of visibility switching.
  1. Limit the amount of work needed for the two source strings Do not hide toolbar and Do not hide status bar by simply using only one translation for both them: Do not toggle this bar by TAB key. Perhaps the lazy Canadians are going to use this translation for Do not hide toolbar and menu too.
  1. Honor the importance of the Working mode in JOSM.
    • When the Canadians see a mode they are not stingy with words and call it a mode. For example:
      Select mode - Select, move, scale and rotate objects instead of Select, move, scale and rotate objects
      Extrude mode - Create areas, move way segments instead of Create areas
      Zoom mode - Zoom and pan map instead of Zoom and pan map

    • But when the people south of their border want them to call something a mode what clearly is not a mode the Canadians get angry and use their dialect to say
      Expert view instead of Expert mode.
  1. Harmonize the Preferences dialog tab names to <name> preferences instead of <name> [settings|customization|Preferences|].
  1. Avoid SPACE and three dots in their menus if these characters are not needed. So they use
    Undo instead of Undo... and
    Redo instead of Redo... because these commands acts without a following dialog.
    Downloading open changesets... because not SPACEis needed in front of the dots.

Feel free to hear from the friendly Canadians.

Attachments (0)

Change History (14)

comment:1 Changed 2 months ago by Hb---

Description: modified (diff)

comment:2 Changed 2 months ago by Don-vip

Keywords: canada added

comment:3 Changed 2 months ago by Don-vip

Milestone: 19.02

comment:4 Changed 2 months ago by Don-vip

In 14811/josm:

see #17380 - enable en_CA

comment:5 Changed 2 months ago by Don-vip

In 14812/josm:

see #17380 - i18n update

comment:6 Changed 2 months ago by Don-vip

Can you please try r14812 (I just have released it as new latest). It contains translations up to yesterday.

comment:7 Changed 2 months ago by Hb---

en_CA is a choseable now. But the translation from yesterday is not yet delivered, like in all other languages too.

comment:8 in reply to:  4 Changed 2 months ago by stoecker

Replying to Don-vip:

In 14811/josm:

see #17380 - enable en_CA

If Java and JOSM codes don't match very likely trunk/src/org/openstreetmap/josm/tools/LanguageInfo.java must be adapted as well.

comment:9 Changed 2 months ago by Don-vip

@Hb--: "Yesterday" meant 23/02, not 24/02. Do you see any translation made before 23?

comment:10 Changed 2 months ago by Hb---

Resolution: fixed
Status: newclosed

Import notification email date was 24 Feb 2019 10:03:09 UTC.

In version 14813 on About JOSM, Info tab Home page can be seen instead of Homepage. Translation is in https://translations.launchpad.net/josm/trunk/+pots/josm/en_CA/10/+translate

comment:11 Changed 2 weeks ago by Klumbumbus

The current situation with en_CA is not good. It is named canadian english but published as "easy" english (Java OpenStreetMap Editor in Easy English, This ''Canadian'' language variant uses simpler terms and The Canadian variant is not meant as translation.).

  • If it is canadian english then the canadian "dialect" should be used regardless if it is simple or complex language
  • If it is simple english it should be renamed to "Simple english" or "English (simple)" or "Basic english" or whatever the common used term is.

See also https://forum.openstreetmap.org/viewtopic.php?id=65793

Last edited 2 weeks ago by Klumbumbus (previous) (diff)

comment:12 Changed 2 weeks ago by Don-vip

Ah, It seems I completely missed the point of this translation, my bad :(
If this is "Basic English" (https://en.wikipedia.org/wiki/Basic_English) I agree we shouldn't hijack the Canadian locale for this, but I have no better idea. The IETF code "en-basiceng" doesn't seem supported by Launchpad.
If this is "Canadian English" (https://en.wikipedia.org/wiki/Canadian_English) then I agree we shouldn't talk about it being simple or not.

comment:13 Changed 2 weeks ago by Klumbumbus

@Hb---: did you add most of the en_CA strings to Launchpad? Are they in any way related to canadian english?

comment:14 in reply to:  11 Changed 13 days ago by Hb---

JOSM has a stagnating and dropping support of translators. One of the reasons is the partly complicated ("Select the selected") and inconsistent wording (comment:1) of the user interface. (Additionally this makes JOSM hard to learn too.)

To overcome this, a glossary is needed (#15872) and some source strings need to be replaced (#15918). Changing strings in the source based on a patch file has some disadvantages: It would immediately kill all existing translations and a test run for other translators is nearly impossible.

So a dialect was used to easily show the suggested string replacements in effect. Because of its presence in Launchpad and the amount of three(!) translated strings since 2010 the en_CA was chosen for this test run.

The dialect can be provided under the en_US localization as well. This may help to avoid confusion.

The plan is:

  1. Achieve consent about the future strings with the help of the glossary and the dialect localization.
  2. Offer the new strings in a temporarily source code file to all translators.
  3. Give time to translate.
  4. Replace the former strings with the new strings in the appropriate source code files.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.