Instead of just linking directly to the source file going further sounds better
Eg a line
Located in ../path/to/file.c:77
should link to all translations within that file (or folder), so that translation can be done per logical units (split into files or folders)
eg above line enriched with such links would become:
Located in <a href="+translate?path=..">..</a>/<a href="+translate?path=../path">path</a>/<a href="+translate?path=../path/to">to</a>/<a href="+translate?path=../path/to/file.c">file.c:<a href="http://code.launchpadp.net/project/trunk/path/to/file.c#77">77</a>
new llinks such as:
- "+translate?path=../path/to/file.c" = listing all translatable strings in that file
- "+translate?path=../path" = listing all translatable strings in that folder
need to be supported
Instead of just linking directly to the source file going further sounds better to/file. c:77
Eg a line
Located in ../path/
should link to all translations within that file (or folder), so that translation can be done per logical units (split into files or folders)
eg above line enriched with such links would become: translate? path=.. ">..</a> /<a href="+ translate? path=.. /path"> path</a> /<a href="+ translate? path=.. /path/to" >to</a> /<a href="+ translate? path=.. /path/to/ file.c" >file.c: <a href="http:// code.launchpadp .net/project/ trunk/path/ to/file. c#77">77</a>
Located in <a href="+
new llinks such as: path=.. /path/to/ file.c" = listing all translatable strings in that file path=.. /path" = listing all translatable strings in that folder
- "+translate?
- "+translate?
need to be supported