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

german translation for shortcuts #1870

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

juli-99
Copy link
Contributor

@juli-99 juli-99 commented Sep 14, 2023

No description provided.

hotkeyAutoLabelOpen = Label bearbeiten
hotkeyAutoLabelToggle = Label sichtbarkei umschalten
hotkeyAutoLabelView = Label anzeigen
hotkeyAutoLabelHide = Label ausblenden
# ==> hotkeyAutoLabelSelfNumberedStop =
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I could not think of a good translation for "End Self Numbered Function".

Copy link
Member

Choose a reason for hiding this comment

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

I took some time today to actually understand the context of AutoLabelSelfNumberStop. Here is how you can observe its use.

Open a new document. Select a component with a label: I picked a register. Drag one out toward the canvas but do not drop it. Press the lower case L. A popup allows you to enter a label. Pick a label ending in a number: I picked "R1". Now drop the component. It should show with the selected label. Now drag another one onto the canvas and drop it. It should show with the next label, e.g. "R2". Each new one increments the number.

Now suppose you wish to drag one out and not label it. While dragging, press lower case A. That is the AutoLabelSelfNumberStop issue. When you drop it, it is not labeled.

@juli-99 and @MarcinOrlowski: I propose "Stop auto-numbering labels" as a better description in English. But @MarcinOrlowski is correct that getting the context for translation in a short description is pretty difficult. This panel is not the documentation for how to use the key. It allows someone that knows how to use the key to change the key to use.

Note that the Label open action (L) works as described above if using it while dragging out the component. But it also works to apply a label on a selected component that is already placed, but does not start auto-numbering in that case. Many of these keys can also be used on selected items already placed on the canvas.

Comment on lines +653 to +654
hotkeyProjMoveUp = Schaltung nach oben
hotkeyProjMoveDown = Schaltung nach unten
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not happy with this translation because without the context it is difficult to guess what it does.

The English versions "Move the Circuit Up Layer" and "the Circuit Down Layer" are not that great either.

Copy link
Member

Choose a reason for hiding this comment

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

The actual menu items in English are "Move Circuit Up" and "Move Circuit Down"

As I mentioned in #1861, the name in the panel should match the name in the menu. So this should be changed to "Move circuit up" (or "down") to match the case as done in #1861. The same concept should likely apply in the other languages. @MarcinOrlowski: could you change this in #1861? Or alternatively, would it work to actually take the string from the menu item and not duplicate the information?

Copy link
Member

Choose a reason for hiding this comment

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

@davidhutchens Done as requrested.

BTW: to be honest I got a feeling the "English" strings for that sections are low quality and somehow slipped by during the review.

Or alternatively, would it work to actually take the string from the menu item and not duplicate the information?

I am not fully convinced this is a good idea. This kind of "optimizations" sometimes bites back when you try to translate the strings. What we do lack is context so the translators can ensure they see what they do which is not always the case. Not sure how to approach that.

Copy link
Member

Choose a reason for hiding this comment

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

@MarcinOrlowski: I don't do translation to non-English languages, but I can appreciate why trying to automatically generate strings could cause problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants