IIRC, you do not say a b'racha in that case, or in any case involving either a forced or a condoned violation of halacha (the canonical example is a sick person or pregnant woman eating or drinking as medically required on Yom Kippur).
I think you have the principle correct but the example incorrect. Someone with a medical exemption on Y"K is not violating halacha (halacha itself has created the exemption) and therefore does make brachot. In fact, one of the reasons we chose the wedding bencher we did is that it includes the ya'aleh v'yavo for Y"K.
And, gufa (i..e, back to the main subject), yiyasher kochachen to Monica! (FWIW, when I'm reading from a prepared text, I usually go with 28-point text leaded by an extra 50%; I find the leading more important than the font size. On the other hand, you can end up with text that's too large; our shul just got a new haftarah book and the text is so large that some of the longer words don't fit in my field of vision. It's very embarassing so start reading one word and discover halfway through that it's another; it's also embarassing to pause before any long word to read it through once silently before chanting it aloud. Grumble.)
In fact, one of the reasons we chose the wedding bencher we did is that it includes the ya'aleh v'yavo for Y"K.
I never would have thought to look for that. Thanks for the interesting discussion.
And, gufa (i..e, back to the main subject), yiyasher kochachen to Monica!
Thank you!
Thanks for the tip on leading. I hadn't thought about that. I do worry about text getting too large; for people's names (for the aliyot) on Saturday I used 36-point, and Hebrew names tended to occupy two lines (we include mothers -- e.g. Ploni ben Avraham v'Rachel). That would definitely have been overkill for the d'var torah (or translations), but it's worth exploring things between 24 (worked) and that. I'll see what 28 looks like.
For haftarah, my rabbi reads straight from a regular chumash (more power to him; I couldn't do that) and the b'nei mitzvah get individual print-outs, I think from Trope Trainer, that seem to be of a decent size. We don't have a dedicated book. (Well, we probably have several, but we don't use one that I've ever seen.)
I think you have the principle correct but the example incorrect. Someone with a medical exemption on Y"K is not violating halacha (halacha itself has created the exemption) and therefore does make brachot. In fact, one of the reasons we chose the wedding bencher we did is that it includes the ya'aleh v'yavo for Y"K.
And, gufa (i..e, back to the main subject), yiyasher kochachen to Monica! (FWIW, when I'm reading from a prepared text, I usually go with 28-point text leaded by an extra 50%; I find the leading more important than the font size. On the other hand, you can end up with text that's too large; our shul just got a new haftarah book and the text is so large that some of the longer words don't fit in my field of vision. It's very embarassing so start reading one word and discover halfway through that it's another; it's also embarassing to pause before any long word to read it through once silently before chanting it aloud. Grumble.)
Reply
I never would have thought to look for that. Thanks for the interesting discussion.
And, gufa (i..e, back to the main subject), yiyasher kochachen to Monica!
Thank you!
Thanks for the tip on leading. I hadn't thought about that. I do worry about text getting too large; for people's names (for the aliyot) on Saturday I used 36-point, and Hebrew names tended to occupy two lines (we include mothers -- e.g. Ploni ben Avraham v'Rachel). That would definitely have been overkill for the d'var torah (or translations), but it's worth exploring things between 24 (worked) and that. I'll see what 28 looks like.
For haftarah, my rabbi reads straight from a regular chumash (more power to him; I couldn't do that) and the b'nei mitzvah get individual print-outs, I think from Trope Trainer, that seem to be of a decent size. We don't have a dedicated book. (Well, we probably have several, but we don't use one that I've ever seen.)
Reply
Leave a comment