<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><span>The safer method for Chinese, Japanese, Korean, Thai, Burmese, and some lesser punctuated languages like Haitian Creole is to use a number with a circle around it. This is found as a standard in Japanese typesetting and generally accepted in field testing. We've even considered using this for Cyrillic and Latin, as it is seen in some cases and would work. It will not work well for some Devanagri and Arabic scripts which use alternate numbers. This Circle number method is a lot closer to universal that the issues you will run into trying to shrink and superscript some scripts. </span></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 16px; color: rgb(0, 0, 0); background-color: transparent;
font-style: normal;"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 16px; color: rgb(0, 0, 0); background-color: transparent; font-style: normal;">There are unicode points starting at U2460, but they jump around to the maximum of circle-50. </div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 16px; color: rgb(0, 0, 0); background-color: transparent; font-style: normal;"><br></div><div style="background-color: transparent;">01-20 U2460-U2473 http://www.fileformat.info/info/unicode/block/enclosed_alphanumerics/index.htm <br></div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; font-style: normal;">21-35 U3251-U325F</div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; font-style:
normal;">36-50 U32B1-U32BF </div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; font-style: normal;"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><br></div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> David Haslam <dfhmch@googlemail.com><br> <b><span style="font-weight: bold;">To:</span></b> sword-devel@crosswire.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, February 19, 2013 9:21 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> [sword-devel] Generated footnote markers in non-Roman modules<br> </font> </div> <br>
Some Bible modules that are for a language with a non-Roman script do NOT<br>have an attribute 'n' value in the OSIS,<br>so the automatically generated footnote markers (a, b, c, d, ...) look<br>especially bad.<br><br>If at all possible, we should employ letters from the same script.<br><br>For collaboration projects, this subject should be something to be reviewed<br>with the copyright owners and/or Bible translators.<br><br>/This was briefly commented on in a private email concerning the Central<br>Kurdish (Sorani NT) module/.<br><br>David<br><br><br><br>--<br>View this message in context: http://sword-dev.350566.n4.nabble.com/Generated-footnote-markers-in-non-Roman-modules-tp4651985.html<br>Sent from the SWORD Dev mailing list archive at <a target="_blank" href="http://nabble.com/">Nabble.com</a>.<br><br>_______________________________________________<br>sword-devel mailing list: <a ymailto="mailto:sword-devel@crosswire.org"
href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/sword-devel<br>Instructions to unsubscribe/change your settings at above page<br><br><br> </div> </div> </div></body></html>