Comment 1 by mdcurran on 2011-05-31 22:45
We have considered this before. But, the issue is that there is two separate symbols for line feed and carage return, and in some editors or documents you can arrow to both. What should NVDA say different for each? It can't say line or line end for both as this would then seem as though there were two line breaks, which was not the case.
Users can now rename their symbols if they have a problem with this.
If someone can come up with simpler turms for each, with out making it ambiguous, I'm sure we can take them, but for now in my opinion line feed and carage return are the most accurate.

Comment 2 by jteh on 2011-06-01 00:04
Adjusting summary to cover one specific issue, as again, this ticket is otherwise too broad.
Changes:
Changed title from "Language terms for how NVDA tells user of the information should be revised." to "Make "line feed" and "carriage return" symbol names more user friendly"

Comment 3 by briang1 on 2011-06-01 07:44
My main argument of one of these which needs changing is line for underscore, as it can be confusing if you have line numbers in a document. However now we have the ability to edit all of these words, I feel that people can configure it to suit their circumstances quite easily, thus if you want complex descriptions of what line feed and carriage return are, or not its up to you really.

Does anyone have more user-friendly alternatives to line feed and carriage returned at present? Also, even before considering any proposed alternatives, we must keep in mind the fact that these two terms have been in NVDA since many years now and changing them may result in potential confusion. If no one disagrees, I would like to kindly suggest closing this ticket as invalid. @ehollig

Closing as invalid since the user can configure it for his or her needs.