Home → Feedback →

use the term keyserver (as used in the man pages) consistently

• Edit

Helmut K. C. Tessarek

17 Jun, 2015 07:51 PM

According to different sources there are 2 ways to spell keyserver. I've taken the term keyserver from the gpg man pages and
I've opened a pull request which consistently uses the term keyserver in the menu and the context menu.

https://github.com/GPGTools/GPGKeychainAccess/pull/18

1. Support Staff 1 Posted by Luke Le on 17 Jun, 2015 09:57 PM

   

   Hi Tessarek,

   thank you for the pull request!
   We should definitely implement this consistently and always use one of the two spellings, but I don't think "Keyserver" is the right spelling in english.
   The use of "keyserver" in gpg man pages might stem from the fact that the main developer of gnupg is german himself.

   The fact that our main language is also german might have influence our use of "keyserver". Are you by any chance a native english speaker?

   • Edit

2. 2 Posted by Helmut K. C. Te... on 17 Jun, 2015 10:09 PM

   

   If you check https://en.wikipedia.org/wiki/Key_server_%28cryptographic%29 you will see that 99% of the article the term keyserver is used. I think the only time they used 'key server' was in the first paragraph. If you google it, the first few result pages are filled with the term 'keyserver'.

   I picked the term keyserver over key server because it was more prominent in the sources I could find.

   But I don't really care as long as it is consistent.

   • Edit

3. Support Staff 3 Posted by Luke Le on 17 Jun, 2015 10:13 PM

   

   Interesting, it's quite a mess even in that wikipedia article.
   I personally also prefer keyserver (haha, and right now Apple is trying to spell check it and have me either correct it to "key server" or "key-server")

   • Edit

4. 4 Posted by Helmut K. C. Te... on 17 Jun, 2015 10:26 PM

   

   Yea, I'm puzzled about the correct spelling myself, but as far as I could tell keyserver was used in most articles and/or web pages.

   I couldn't find an entry in merriam-webster's dictionary either.

   I think all 3 are actually valid.

   • Edit

5. Support Staff 5 Posted by Steve on 18 Aug, 2015 02:52 PM

   

   Hi Helmut,

   we have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.

   We need to deal with this although it will stir up a lot of dust in the localization system. I absolutely agree this should be unified.

   Kindly,
   steve

   • Edit

6. Steve closed this discussion on 18 Aug, 2015 02:52 PM.

7. Helmut K. C. Tessarek re-opened this discussion on 05 Jul, 2016 06:36 PM

8. 6 Posted by Helmut K. C. Te... on 05 Jul, 2016 06:36 PM

   

   Hi Steve,

   it's still not consistent btw.

   in the menu: key server
   in the context menu: Keyserver

   as mentioned in https://gpgtools.tenderapp.com/discussions/problems/49422-compile-i... there are 2 resource directories for English: en_US.lproj and en.lproj. In Xcode MainMenu.xib and MainMenu.xib (English) point to en.lproj. But when you change something and re-compile, nothing happens.

   It took me 3 hours to find out that you can't change the GUI from Xcode unless you specifically open the xib files in the en_US.lproj directory.

   I suspect the key server inconsistencies happened because people change some stuff in en_US.lproj and other stuff in en.lproj.

   • Edit

9. Helmut K. C. Tessarek closed this discussion on 06 Jul, 2016 02:56 PM.

10. Steve re-opened this discussion on 11 Jul, 2016 12:02 PM

11. Support Staff 7 Posted by Steve on 01 Aug, 2016 06:23 PM

    

    Hi Helmut,

    this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.

    Should the problem persist, please re-open this discussion and let us know. For more questions that are not related to this specific problem, you are welcome to create a new discussion any time.

    Best, steve

    Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.

    • Edit

12. Steve closed this discussion on 12 Aug, 2016 03:15 PM.