[GRASS-dev] [GRASS GIS] #1936: wxGUI command console: "Protocol" isn't really the right word & cleanup

[GRASS GIS]

#1936: wxGUI command console: "Protocol" isn't really the right word & cleanup
-----------------------------+----------------------------------------------
 Reporter:  hamish           |       Owner:  grass-dev@…              
     Type:  defect           |      Status:  new                      
 Priority:  normal           |   Milestone:  6.4.3                    
Component:  wxGUI            |     Version:  unspecified              
 Keywords:  command console  |    Platform:  Unspecified              
      Cpu:  Unspecified      |  
-----------------------------+----------------------------------------------

Comment(by hamish):

 I'm curious about this, can you say what "journal" translates to for you?
 (considering that it will not always appear as translated)

 From my personal, but native speaker, POV "Journal" is the best
 of the lot. You'll see it also used for "journaling file system",
 it's traditionally a personal book you keep notes in, and in
 finance as "journaled the expense into the ledger".
 It seems to me something like "The Wall Street Journal" is a bit of
 a colloquialism or play on financial words.


 "Log" could work, but I'd expand it to "command log" or "log history"
 or something like that. I work on ships a quite a bit and the
 ship's log, where all maintenance, events, and details of the current
 situation at shift changes are noted, is still heavily used.

 The difference between journal and log might be that log is a bit
 more of a formal record of events.

 "Log file" might be ok too, but it could suggest that the entire session
 would be logged, including output. Everyone would know exactly what it
 meant though, so maybe a winner there.

 The great "ah-ha" moment comes when the user realizes that they can
 'chmod u+x' the file or rename it to ".bat", and they instantly have
 a runable shell script for their workflow. Super-low barrier entry
 to scripting/writing their first program. Typically that will want
 some editing and cleanup first, so the "scratch pad" idea of a journal
 appeals to me more than the frozen history/archive meaning that a
 log instills.

 iPython has gone with "notebook", but I think that's too much of an
 interactive meaning for what the button does.

 As for "Record", that sounds to me more like a screencast sort of
 thing, or a button for keeping audio notes. Or at least someone
 somewhere will misinterprept it as that.


 It's all just semantics of course with no right answer, but the
 choice of words can make all the difference in providing subtle clues
 to the user about the meaning of the tool.


 The "Protocol" meaning doesn't help the programmer understand much
 at all what it is talking about, they are more likely to think it
 has to do with some communication API, so I'd change it everywhere.
 It's only 10-20 lines.

 Martin:
 > I would tend to agree with Vaclav, "journal" in this meaning is
 > quite cryptic for non-native speaker.

 perhaps, but it also seems to me to be the most correct.
 what other meaning/idea do you get from it?


 shrug,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1936#comment:5>
GRASS GIS <http://grass.osgeo.org>