--
Joan,
a) I did an advanced search in Google "Christian Hebraists" and chronogram and
retrieve (3 items), among them this one
http://www.smitskamp.nl/650-RAR.HTM
Rare Books & Manuscripts January 2005 LURIA, SOLOMON BEN JEHIEL. Hokhmat
Shelomo. * Vienna, gedruckt bei Georg Hraschanzky, K. K.
I don't know much about Roman script cataloging and especially older books
(I may ask my wife, she has more experience with those old rare books),
and I don't remember seeing chronograms in Yiddish books (although, books
might be in Yiddish, but the title page would be in Hebrew, especially if
w
This author has been established (nr2005009039) as "Ibgi, Haviv" (by me, I did
it). I chose "Ibgi" instead of "Ivgi" because of Moshe Ibgui (nr2005009039),
whose name appears in a nonstandard romanization. I'll add a reference from
"Ivgi." --Joan
>>> [EMAIL PROTECTED] 07/19/05 3:21 PM >>>
Fo
Do we know of any roman script books that contain chronograms? Do we know of
them in any language other than Hebrew? Are there any Yiddish chronograms?
Joan
>>> [EMAIL PROTECTED] 07/19/05 2:38 PM >>>
I haven't been following this discussion that closely,
but what is generally done in roman scr
The option of recording the source of a chronogram could be considered a local
practice. Transcribing the whole chronogram in a note seems more important to
me, but (IMHO!) I think a description of such a practice belongs in HCM, not in
RDA.
Joan
>>> [EMAIL PROTECTED] 07/19/05 2:56 PM >>>
I
thanks yossi.
b
At 03:28 PM 7/19/2005 -0400, you wrote:
and Mikud is not a place name but the Hebrew word for ZIP-Code ...
At 03:21 PM 7/19/2005, you wrote:
Folks:
I've got a book the author of which has one of those very special last
names that might require a provisional status. the nam
and Mikud is not a place name but the Hebrew word for ZIP-Code ...
At 03:21 PM 7/19/2005, you wrote:
Folks:
I've got a book the author of which has one of those very special last
names that might require a provisional status. the name: .Haviv
[alef-yud-bet-gimel-yud]. yes, it looks like
It is Ivgi
Yossi
At 03:21 PM 7/19/2005, you wrote:
Folks:
I've got a book the author of which has one of those very special last
names that might require a provisional status. the name:
.Haviv [alef-yud-bet-gimel-yud]. yes, it looks like ivgi, but it
could also be ibgi, ebgi, or evgi. i thin
Folks:
I've got a book the author of which has one of those very special last
names that might require a provisional status. the name: .Haviv
[alef-yud-bet-gimel-yud]. yes, it looks like ivgi, but it could also be
ibgi, ebgi, or evgi. i think the form two are better guesses than the
latte
Again, I think it should be a local decision by the Cataloging agency and
not a mandated or even mentioning it as optional (I am sure Library
administrators will hate the fact that we are spending hours looking
through the whole pile of the Talmud to find the correct verse)
Yossi
At 02:56 PM
IMHO, I do not think that *identifying* the source of the chronogram is
bibliographically significant, and would advise against incorprating this idea
into the rules, even on an optional basis.
My understanding is that we should be thinking in terms of recommendations that
make the rules easi
I agree, but there's no reason why it can't be an optional note.
- Original Message -
From: "Yossi Galron" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 19, 2005 12:27 PM
Subject: Re: proposed draft RDA rule on 260s
>
> I don't think adding the source is adding much to the bibliographic
I haven't been following this discussion that closely,
but what is generally done in roman script books that
contain chronograms?
I would expect something like,
in the 260, having the chronogram transcribed with the
derived date in brackets,
with a 5xx describing the chronogram and how the date
wa
I don't think adding the source is adding much to the bibliographic
information (if at all).
I wouldn't mandate it, but if a cataloger wants to add it - it should be
done in a note and not in the 260 field.
At 12:07 PM 7/19/2005, you wrote:
I like this idea! And I'm quite willing to transcr
Perhaps the colon was a bad example. What I had in mind initially was that
the AACR2 states, "Transcribe the title proper exactly as to wording, order,
and spelling, but not neccessarily as to punctuation and capitalization"
(1.1B1). If this rule had an equal with regard to the Publication Area,
I like this idea! And I'm quite willing to transcribe the whole chronogram in
a note--my only question is whether the SOURCE of the chronogram ("Ps. 92:12"
or the like)--not the CONTENT of the chronogram, whether or not it refers to
the content of the item or the author's name-- is bibliographi
Some alternative approaches include:
Transcribing the entire chronogram followed by a bracketed Hebrew date
For complex chronograms in which only selected letters comprise the date, just
supply a bracketed Hebrew date. The entire chronogram could then be
transcribed (optionally) in a note.
Len
But in both the roman and the nonroman field, and maybe ESPECIALLY in the
nonroman field, we are supposed to be transcribing what we see within subfields
demarcated by prescribed punctuation. There's no difference between roman and
nonroman regarding either prescribed (required) punctuation or
I am not sure I understand the problem.
I wouldn't change the practice that we do regarding the chronogram IN THE
ROMANIZED FIELD. I would use the Geresh only for the 260 field in the
Hebrew script.
Yossi
At 10:45 AM 7/19/2005, you wrote:
Interesting argument, but the colon between the place
Interesting argument, but the colon between the place of publication and the
publisher's name is so-called "prescribed punctuation," required by the rules
of International Standard Bibliographic Description to demarcate subfields.
Slashes and periods and semicolons are prescribed punctuation to
Geresh is a punctuation mark, and don't we generally add punctuation marks
to our records so that they can be better understood?
In most cases, a colon generally does not appear on the item between the
place of publication and the publisher's name, but we include it there in
order to add context to
21 matches
Mail list logo
