Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clear labels for OSM hyperlinks in history panel (OSM history & OSM Profile) #8834

Merged

Conversation

jasonghent98
Copy link
Contributor

Hi! I saw that there were no accepted pull requests to this issue, so I decided to take a stab at it to make it a little clearer in the history panel. I hope this works!

@tyrasd
Copy link
Member

tyrasd commented Dec 2, 2021

this is for issue #8784

Copy link
Member

@tyrasd tyrasd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please also change the label of the changeset link to osm as well (currently line 79)?

I'm wondering if we should make these texts translatable. I think it would not hurt. I can change that for you if you're not feeling comfortable, but it would need additional entries in data/core.yaml and the translated text needs to be appended here using .call(t.append(…)) instead of .text(…). See line 24 for an example.

//edit: there are also a few minor code style issues (a missing ; and some superfluous space) to be fixed, see: https://github.com/openstreetmap/iD/pull/8834/files

@tyrasd tyrasd added the usability An issue with ease-of-use or design label Dec 2, 2021
…tion; removed trailing spaces in modules/operations/split.js & modules/ui/fields/input.js; fixed if statement with brackets on line 224 in modules/ui/fields/input.js
@jasonghent98
Copy link
Contributor Author

Hi,
Let me know if that looks better. In regards to making the texts translatable, are you referring to the core.yaml file itself, or rather the texts within the OSM history panel links (history, profile, changeset)? If the first, I could probably just use a third-party tool like iCanLocalize to do that. If the latter, I can also take care of that within the yaml file.

modules/ui/panels/history.js Outdated Show resolved Hide resolved
…)) and added a corresponding entry point in core/yaml
@tyrasd
Copy link
Member

tyrasd commented Dec 6, 2021

In regards to making the texts translatable, are you referring to the core.yaml file itself, or rather the texts within the OSM history panel links (history, profile, changeset)?

I was referring to the texts of the links in the history panel. I've just written a small tutorial about how to do that here: https://github.com/openstreetmap/iD/wiki/How-to-use-iD%27s-localizer-module

@jasonghent98
Copy link
Contributor Author

Thanks for the clarification. Let me know how this looks.

Copy link
Member

@tyrasd tyrasd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's almost done! Only two more things:

  1. drop the .text('…') lines (lines 44, 81 and 204). The text adding is done already with the .call(t.append(…));
  2. start all new strings in capital letters perhaps?

@tyrasd tyrasd merged commit 8111e5d into openstreetmap:develop Dec 7, 2021
@tyrasd tyrasd mentioned this pull request Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability An issue with ease-of-use or design
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants