As I'm going through and translating the strings extracted by tmpl_process3.pl, I'm finding there is about 50% French text. Is that redundant? I am hoping to translate from English only so it would speed up the process if I could weed out the redundant text. Also, there is some unfamiliar slang or jargon and some other things which are a little hard to translate out of context (i.e. using a .po file and kbabel). Could I ask for a little clarification or confirmation/denial of my initial guesses? Specifically, * what are "tags"? MARC/UNIMARC/MARC21 fields? e.g.: mandatory "tags" empty * what is "Biblio"? A bibliographic record? * What do "biblionumber" and "biblioitemnumber" refer to? Is one the metadata and the other the instance / physical artifact? Also, is there a recommended writing style guide? Also, going through the strings, I can see some easy places for improvement: * The use of "click", as in "can be clicked", is hardware/software dependent and should be avoided in favor of some other wording. * white space inside hyperlinks e.g. <a1> foo </a> instead of <a1>foo</a> could be removed * as can space before punctuation, e.g. " :" instead of ":" A slightly more labor intensive change would be to use more CSS for layout in the future versiosn so that we don't continue to use high repetitions of for horziontal layout. -Lars ------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/
On 2004-09-20 13:10:01 +0100 lars@rovaniemelainen.com wrote:
* what is "Biblio"? A bibliographic record? * What do "biblionumber" and "biblioitemnumber" refer to? Is one the metadata and the other the instance / physical artifact?
As I understand it, your guesses are correct. biblionumber is the number of a bibliographic record, while biblioitemnumber is the number of a particular item's bibliographic info.
Also, is there a recommended writing style guide?
Not that I know of, but all of your suggestions should be in it, at least for English. (I know French differs on punctuation and spaces.) Care to search on the wiki for one and start one if not?
A slightly more labor intensive change would be to use more CSS for layout in the future versiosn so that we don't continue to use high repetitions of for horziontal layout.
There are CSS-based templates for OPAC. I'm not sure about intranet. It definitely should be an aim IMO. -- MJR/slef My Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ http://www.thewalks.co.uk stand 13,Lynn Carnival,12 Sep
lars@rovaniemelainen.com said:
Could I ask for a little clarification or confirmation/denial of my initial guesses? Specifically,
* what are "tags"? MARC/UNIMARC/MARC21 fields? e.g.: mandatory "tags" empty
"fields" or "field identifiers" will work, depending on whether you are talking about the tag itself or the data identified by the tag. Here's the Library of Congress' description (from http://www.loc.gov/marc/96principl.html): 6. Variable Fields and Tags 6.1. The data in a MARC record is organized into fields, each identified by a three-character tag. 6.2. According to ANSI Z39.2, the tag must consist of alphabetic or numeric ASCII graphic characters, i.e., decimal integers 0-9 or letters A-Z (uppercase or lowercase, but not both). The MARC 21 formats have used only numeric tags. 6.3. The tag is stored in the directory entry for the field, not in the field itself. -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
participants (3)
-
lars@rovaniemelainen.com -
MJ Ray -
Stephen Hedges