3. 
3.5.2. Formatting language
Formatting language (FL) to design output citation styles |
|||||||||||
| Bibus | EndNoteWeb | RefWorks (web based) | Procite | EndNote | Reference Manager | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
 |
 |
 |
 |
 |
 |
||||||
1 - General features |
|||||||||||
| Bibus : there is not explicit formatting language: all the settings are done via mouse selection of predefined options: basic structure patterns is represented by OOw bibliographic module |
EW: n.a. since the citation styles are not modificable via EW: they can only be uploaded from EndNote desktop by Administrator login. Therefore to use the formatting language must use EndNote desktop |
RW: made up of coded field names, text strings (alone or in front and/or after fields), punctuation, separators, style (italics etc.), tab, carriage return, page break; many options for names;
(FL recognizes field names specifically belonging to each individual RT) |
Pr: mostly made up of:
1 field names 2 two formal instructions: field/string separator, group command «...» (i.e. if more elements -fields- are included in a group, one is enough for the relevant surrounding punctuation to be output) 3 text strings, punctuation (automatic control on double punct.), spacing, style (B I U etc.): as written 4 many options for names, titles, dates, pages, keywords varying by RT and output context 5 back slash \ (ASCII 92) marks any string as mere text, e.g.: " \« " FL recognizes RT specific, not generic, workform fields names and not numbers (therefore be careful when copying definitions from one workform to another) |
En: mostly made up of:
1: field names 2: field/string separator (|) also useful to put punctuation around a group of fields; link adjacent text (nonbreaking space) 3: text strings, punctuation, spacing, tab, style B I U etc. 4: options for anonymous works, pages and journal names apply to any RT, across any output context (In-text, Footonotes and Bibliography): cannot be differentiated by RT or output context; options for name vary with RT and output context; 5: ` (ASCII 96) marks strings as mere text e.g. overlapping field names `Journal`; 6: handles singular vs plural, e.g. p^pp. ed.^eds. recognizes generic field names |
RM: mostly made up of:
1 field names; 2 two formal instructions: field/string separator, group command «...» (i.e. if more elements -fields- are included in a group, one is enough for the relevant surrounding punctuation to be output); 3 text strings, punctuation (automatic control on double punct.), spacing, style (B I U etc.): as written; 4 many options for names, titles, dates, pages, keywords varying by RT and output context; 5 back slash \ (ASCII 92) marks any string as mere text, e.g.: " \« " same as ProCite, but FL recognizes fields generic names and numbers |
||||||
2 - Selection
|
|||||||||||
| Bibus : 1 | EW: n.a. | RW: 1, subfields just for personal names | Pr: 1; 2: only "surname, name, qualification", internal date format | En: 1; 2: only "surname, name, qualification" | RM: 1; 2: only "surname, name", internal date format | ||||||
3 - Add text strings in front of/after fields content (conditionally: only if there is content, unconditionally: despite the presence of content, i.e. empty fields) |
|||||||||||
| Bibus : yes, unconditionally | EW: n.a. | RW: yes | Pr: yes | En: yes (can handle singular vs plural: p^pp. ed.^eds if start-end pages or more authors are present) | RM: yes | ||||||
4 - Distinguishes among occurrences of a repeatable field
|
|||||||||||
| Bibus : only as far as names are concerned | EW: n.a. | RW: only as far as names are concerned | Pr: only names as far as output and sort are concerned | En: only names as far as output is concerned | RM: only names, as far as output is concerned | ||||||
5 - Produces tagged format output, apart from built-in export routines |
|||||||||||
| Bibus : no | EW: n.a. |
RW: yes (e.g. \nKW: to output a repeatable field occurrences on different lines) |
Pr: yes (e.g. ^pKW: as keywords separator, where ^p are two characters) |
En: to a limited extent
can handle a repeatable field like authors field, but not keywords labelled on consecutive lines, does not handle <CR> as format specification within the same field |
RM: yes (e.g. ¶KW: as keywords separator where ¶ is [ASCII 20]) | ||||||
6 - Offers conditional commands (IF ... THEN ...) |
|||||||||||
| Bibus : no | EW: n.a. | RW: no (implied in many built-in options to be selected for: authors' names, anonymous works ...) | Pr: not explicitly, but implied by various options (e.g. names) | En: not explicitly, but implied by various options (e.g. names) | RM: not explicitly, but implied by various options (e.g. names) | ||||||
7 - Upper/lowercase conversion |
|||||||||||
| Bibus : yes (small caps available) | EW: n.a. | RW: yes for names and titles | Pr: yes (names, titles, sort headings) | En: yes: names -small caps also- titles + list of words that should not be altered | RM: yes (names, titles) | ||||||
8 - Look-up tables to expand acronyms, abbreviations, replace text |
|||||||||||
| Bibus : only Journal list bearing three forms (possibly: Full form, abbrev1, abbrev2) | EW: n.a. | RW: no
(short Journal Title is actually a specific field content in each record, linked to a look-up/index list) |
Pr: yes: a) alternate text between "«...»" ; b) field 10: "Journal title" and relevant list(s) |
En: Journal field ("Secondary title") and relevant list
puts in relation Journal's field content and the Journal list's table: a table's record is made up by an entry and three correspondent strings, most often abbreviations; this way you can handle periodical titles and their abbreviations |
RM: Periodical synonyms list | ||||||
9 - Contextual Record Preview while designing a style |
|||||||||||
| Bibus : yes | EW: n.a. | RW: yes | Pr: yes | En: no | RM: yes | ||||||
10 - Text added in styles can be language dependent for each record
|
|||||||||||
| Bibus : only "month" can depend on Op. Sys. language selected | EW: n.a. | RW: no | Pr: no | En: no | RM: no | ||||||
11 - Checking format syntax |
|||||||||||
| Bibus : no, but not really necessary as "errors are impossible" | EW: n.a. | RW: no | Pr: no | En: no | RM: yes | ||||||
12 - Level of difficulty of the formatting language (FL) |
|||||||||||
| Bibus : easy | EW: n.a. | RW: easy | Pr: rather easy, does not require programming skills | En: rather easy, does not require programming skills | RM: rather easy, does not require programming skills (offers a Wizard function, plus the abovementioned syntax control) | ||||||
| Bibus | EndNoteWeb | RefWorks (web based) | Procite | EndNote | Reference Manager | ||||||
|
|
|
|
|
|
||||||
