Community
Participate
Working Groups
I20080805-1307 Show Annotations only annotates the first line of /org.eclipse.jdt.ui/JavadocHoverStyleSheet.css The problem is probably that the file is saved with Mac line delimiters (\r) but I'm opening it in a workspace with Windows delimiters (\r\n).
Also fails on a Mac (with Unix \n as default).
This looks to be caused by the way CVS response looks like. We receive a single line for the whole file, where we should get a message for every line in the file. Server response: 1.10 (teicher 31-Jul-06): /* Font definitions */\rhtml { font-family: sans-serif; font-size: 9pt; font-style: normal; font-weight: normal; }\rbody, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size:1em; }\rpre { font-family: monospace; }\r\r/* Margins */\r... It appears to me that CVS server ignores single CRs (and probably does the same for single LFs from comment 1) as line ending characters. It would be hard (if possible) to change this on the server, so I guess we'll need to handle this particular issue on the client side.
Is it even legal for the CVS server to store an ASCII-mode (-ko) file with only \r as line delimiter? If not, we can also consider this a server bug and I'll just try to fix the file.
I guess the problem is that the ascii mode wasn't set at the beginning but set later.
>I guess the problem is that the ascii mode wasn't set at the beginning but set >later. Don't know whether the server is supposed to fix the file when the ascii/binary property is changed or whether the client is supposed to do the clean up.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
