-
-
Notifications
You must be signed in to change notification settings - Fork 564
Consistent strings3 #235
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
Consistent strings3 #235
Conversation
…No semantic change.
|
I would keep divemode, divelog, divespot, such as setpoint.. This is because, divers have learned with those english words.. In my opinion, some words should not be translated.
Also maybe another french can check about that "setpoint" translation. |
|
Can we have that conversation on the mailing list. I very much appreciate the push for consistency, but I thing @Ghalr raises some good points. |
|
I will try to setup mailing list right now, but I have no idea how it works. To be honest, I have no idea how to translate correctly "setpoint(s)". |
|
I have a concern also about : EAD, END, EADD, MOD |
|
Big thanks for looking at this. :-) I would like to say, that this pull request has nothing to do with question whether to translate something or not. For the record, I wouldn't translate setpoint to Czech. But this has nothing to do with translations. As @ghair pointed out, "Setpoint" is used most often as one word. We use "Setpoint" in UI, so I only suggest to use it as one word everywhere. "Setpoint" has nothing common with "Dive mode", "Dive log" or "Dive spot". These terms can be considered separately. Subsurface now uses both "Dive mode" and "Divemode" (the same for "Dive log" and "Dive spot"). My intention is to use only one variant. I agree with @ghair, that many divers use some terms in english. But these terms should be spelled correctly. PADI uses "dive log", not "divelog": Let's have a look at number of Google search results: "dive mode" 48,700 "dive log" 235,000 "dive spot" 237,000 I belive that two-words versions are the correct ones. |
|
Good point about "dive mode, dive log, dive spot" google result. But some languages requiert like a lot of characters and space left can be a problem. Also let's imagine that you are using Subsurface with your buddy who do not speak your language, it would be much better if specific terms are in english (not translated). I mean specific term like MOD/END where Open Water divers learnt at school. I do believe then that Subsurface is switch to english language when you met new friends ^^. Divers understand these words regardless of their nationality. |
|
So we could decide not to translate some terms. But what about non Latin scripts? Would you leave these terms in Russian, Hebrew, or Chinese?
…-------- Original Message --------
From: Ghalr <notifications@github.com>
Sent: Mon Mar 06 17:50:32 PST 2017
To: Subsurface-divelog/subsurface <subsurface@noreply.github.com>
Cc: Dirk Hohndel <dirk@hohndel.org>, Comment <comment@noreply.github.com>
Subject: Re: [Subsurface-divelog/subsurface] Consistent strings3 (#235)
Good point for me about "dive mode, dive log, dive spot". But some languages requiert like a lot of characters and space left can be a problem. Also let's imagine that you are using Subsurface with your buddy who do not speak your language, it would be much better if specific terms are in english (not translated).
Divers understand these words regardless of their nationality.
I will never put anything else than MOD inscription on my tanks when I'll dive abroad.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#235 (comment)
|
|
Totally. Any divers will clearly understand what's going on even if they dive with russian or chinese divers who speak with understandable terms. Writing down MOD/END (or anything else) on their tanks will help to understand/communicate a lot more faster and easier than having a translated term. Communication is really important to have a better dive without any issues. This would be the same when filling a tank in a fill station, we do use MOD/END terms. I also found some Dive Computer vs Dive computer. |
|
I really, really, really doubt that.
No, let me be more clear.
I think you are dead wrong.
I know quite a few German divers who's have no idea what you are talking about.
…-------- Original Message --------
From: Ghalr <notifications@github.com>
Sent: Mon Mar 06 18:12:52 PST 2017
To: Subsurface-divelog/subsurface <subsurface@noreply.github.com>
Cc: Dirk Hohndel <dirk@hohndel.org>, Comment <comment@noreply.github.com>
Subject: Re: [Subsurface-divelog/subsurface] Consistent strings3 (#235)
Totally. Any divers will clearly understand what's going on even if they dive with russian or chinese divers. Writing down the term MOD/END (or anything else) on their tanks will help to understand/communicate a lot more faster and easier than having a translated term. Communication is really important for anybody.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#235 (comment)
|
|
About MOD/END terms ? |
|
Yep
…-------- Original Message --------
From: Ghalr <notifications@github.com>
Sent: Mon Mar 06 18:57:52 PST 2017
To: Subsurface-divelog/subsurface <subsurface@noreply.github.com>
Cc: Dirk Hohndel <dirk@hohndel.org>, Comment <comment@noreply.github.com>
Subject: Re: [Subsurface-divelog/subsurface] Consistent strings3 (#235)
About MOD/END terms ?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#235 (comment)
|
|
I'm just sharing my point of view here. |
|
I agree with Martin, the 2 word variants of those strings make more sense to me. |
Last string changes on my list. Some of these might be a little bit controversial. If so, please feel free to cherry-pick whatever you like.