Posted by: John Hudson
Peter, which version of InDesign are you using? There are some known issues with contextual mark positioning in InDesign CS and CS2 ME, which cause the kind of collisions you report. Hopefully this will be resolved in future versions of that program, but you can also expect some improvement when I release SBL Hebrew 2.0, which uses a different method for multiple marks below letters.
Regarding the kerning, I'd need to see the results, but I suspect what you are seeing is the rather crude method by which current versions of the font tries to avoid collision between adjacent marks on narrow letters. I'm not satisfied with this method, and coming up with a more refined approach is one of the things that is delaying release of version 2.0. I know how to improve this, but it is a very time consuming piece of work: I have a very large document consisting of all the pairs of letters with marks below that occur in the Bible text, and I am going through it identifying those that need a kerning adjustment and classifying them according to how large that adjustment needs to be. Then I'll need to translate this into contextual rules for OpenType kerning. The good news from your perspective is that I've already tested the method in InDesign CS2 ME and confirmed that it will work there.
Regarding mark order, yes you can expect different display results depending on the mark order, and this may also vary according to application. As discussed at some length in the font manual, mark order is very important. The new MS Office 2007 and Vista Hebrew layout engines are performing on-the-fly mark re-ordering, so in those contexts it will be less important for the user to employ consistent mark ordering, but it is still a good idea to follow the order specified in the manual.
If you come across problems with SBL Hebrew in a specific application such as InDesign, it is always a good idea to also test the same piece of text in MS Word 2003 or 2007 or, if these are not available, in Notepad. This will give you a pretty good indication whether the problem is in the font or in the application.