charlesloder / hebrewtransliteration Goto Github PK

Remove and About should have the name appended

Add a loading spinner for actions

Change some dependencies to devDependencies

Add:

• description
• author
• License
• keywords

at minimal

Create an about page

Instead of hardcoding the list of transliteration schemas available, populate from the list of schema json files present in the directory.
And when a new schema is uploaded, place in the directory where it can be detected. Maybe add field in the json file for description of the schema.

I was wondering if the following schema could be added. It approximates the guidelines in the Journal of Semitic Studies stylesheet as far as possible.

• I don't think it's possible to recognize short/long vowels(?) to distinguish e.g. i and ī, so I used ī for hireq-yod and i for plain hireq, which may require some manual fixes from the user (what would be helpful for this is a separate field for hireq+meteg and qibbuts+meteg).
• The style guide also prescribes that qamets before hatef qamets be transliterated as long qamets: בַּֽצָּהֳרָֽיִם should be baṣṣå̄hå̆rå̄yim, not baṣṣåhå̆rå̄yim. I am not sure if this can be specified in the current system.
• Tsere-he is not recognized correctly, I'm not sure why: וְהִנֵּ֥ה should be wǝhinnē, not wǝhinnɛ.

Some characters are not displayed well on my system. Would you be opposed to adding the Brill font as an option after Charis SIL but before Times New Roman for the output text area? Here is what I see now (with Times New Roman) vs with Brill:

{
  "VOCAL_SHEVA": "ǝ",
  "HATAF_SEGOL": "ɛ̆",
  "HATAF_PATAH": "ă",
  "HATAF_QAMATS": "å̆",
  "HIRIQ": "i",
  "TSERE": "ē",
  "SEGOL": "ɛ",
  "PATAH": "a",
  "QAMATS": "å̄",
  "HOLAM": "ō",
  "QUBUTS": "u",
  "DAGESH": "",
  "DAGESH_CHAZAQ": true,
  "MAQAF": " ",
  "PASEQ": "",
  "SOF_PASUQ": "",
  "QAMATS_QATAN": "å",
  "FURTIVE_PATAH": "a",
  "HIRIQ_YOD": "ī",
  "TSERE_YOD": "ē",
  "SEGOL_YOD": "ɛ",
  "SHUREQ": "ū",
  "HOLAM_VAV": "ō",
  "QAMATS_HE": "å̄",
  "SEGOL_HE": "ɛ",
  "TSERE_HE": "ē",
  "MS_SUFX": "å̄yw",
  "ALEF": "ʾ",
  "BET_DAGESH": "b",
  "BET": "ḇ",
  "GIMEL": "ḡ",
  "GIMEL_DAGESH": "g",
  "DALET": "ḏ",
  "DALET_DAGESH": "d",
  "HE": "h",
  "VAV": "w",
  "ZAYIN": "z",
  "HET": "ḥ",
  "TET": "ṭ",
  "YOD": "y",
  "FINAL_KAF": "ḵ",
  "KAF": "ḵ",
  "KAF_DAGESH": "k",
  "LAMED": "l",
  "FINAL_MEM": "m",
  "MEM": "m",
  "FINAL_NUN": "n",
  "NUN": "n",
  "SAMEKH": "s",
  "AYIN": "ʿ",
  "FINAL_PE": "p̄",
  "PE": "p̄",
  "PE_DAGESH": "p",
  "FINAL_TSADI": "ṣ",
  "TSADI": "ṣ",
  "QOF": "q",
  "RESH": "r",
  "SHIN": "š",
  "SIN": "ś",
  "TAV": "ṯ",
  "TAV_DAGESH": "t",
  "DIVINE_NAME": "yhwh",
  "SYLLABLE_SEPARATOR": "",
  "ADDITIONAL_FEATURES": [],
  "STRESS_MARKER": {
    "location": "",
    "mark": ""
  },
  "longVowels": true,
  "qametsQatan": true,
  "sqnmlvy": true,
  "wawShureq": true,
  "article": true
}

The title says it all

I found that in general "yǝ-" prefix is added to the tetragrammaton, regardless of what settings. Not sure if I am missing a setting.
For example:
כִּי אִם בְּתוֹרַת יְהוָה, חֶפְצוֹ; וּבְתוֹרָתוֹ יֶהְגֶּה, יוֹמָם וָלָיְלָה.
transliterates to:
kî ʾim bǝtôrat yǝ-adonai ḥepṣô; ûbǝtôrātô yehgê, yômām wālāyǝlâ.
compared to other program
kî ʾim bət̲ôrat̲ ʾăd̲ōnāi, ḥep̲ṣô; ûb̲ət̲ôrāt̲ô yehgeh, yômām wālāyəlāh.

Add the google analytics tag into the head

Goliath transliteration for example - my understanding as per SIL transliteration should be Ḡolyāṯ. Is there a way to handle the accents?
גָּלְיָ֥ת
גָּלְיָת
גָּלְיָת֩
גָּלְיָ֨ת
גָּלְיָ֥ת

There is a lot of user interactivity on this site. It would be better to use components.

I could rewrite this in Astro and host on Netlify. Or, Deno Fresh and host on Deno Deploy

Both live and in development, it appears not to work

When errors are captured, it may be useful to ask for the user's email

remove DS_Store from git; double check that it's in .gitignore

Need to add small and large social media images

Is the output of this word correct? I used SBL Academic in this
עֲרְעֹור--> rǝʿăʿôr
I tested with other transliteration apps like https://www.alittlehebrew.com/transliterate/ and get totally different results with same schema.

In the card footer, add social media icons for myself:

• github
• twitter
• academia
• linkedin
• dev.to

Add a regex check to use a netlify function for the remove page like transliteration

https://friconix.com/faq/

When 11ty v2 is more stable, use edge functions

Docs:

• https://www.learnwithjason.dev/blog/css-color-theme-switcher-no-flash
• https://docs.netlify.com/edge-functions/overview/
• https://www.11ty.dev/blog/eleventy-edge/

Add a footer with contact info

A lot of people try to use this tool w/ unpointed text.

When they do, besides just giving an error, provide helpful feedback instead

Add a schema for ISO 259

Explore this. May be a faster return time

https://docs.netlify.com/netlify-labs/experimental-features/edge-functions/

https://github.com/11ty/is-land

See here

Maybe something like:

If there is an error, have a modal that pre-fills a form with browser, the error message, and the input text.

Possibly, not even have the modal, and use a Netlify function to send that data to a google form and then I can get alerted?

See schema here

Add a verse/selection picker using sefaria's api

Like this, make sure I'm using semantic html elements correctly

See here

When user preference is dark mode, there is a flash of inaccurate color

https://github.com/jpoehls/bible-metadata

In cases of more then one vowel on a letter the sequence messes it up
eg: יְרְוּשָׁלִָֽם
is sequeced as יְרְוּשָׁלִָֽם
which is a mistake.
this is the two words in hex
יְרְוּשָׁלִָֽם
יְרְוּשָׁלִָֽם

See here

The Latin character after the Divine Name is dropped

Hebrew

כִּי אִם בְּתוֹרַת יְהוָה, חֶפְצוֹ; וּבְתוֹרָתוֹ יֶהְגֶּה, יוֹמָם וָלָיְלָה

Transliteration

kî ʾim bǝtôrat yhwh ḥepṣô; ûbǝtôrātô yehgê, yômām wālāyǝlâ

The aleph and ayin in SBL General should be apostrophe's not half- rings.

Use FA module in build step https://fontawesome.com/v5/docs/web/setup/use-package-managers

or maybe https://github.com/vidhill/fortawesome-solid-svg-11ty-shortcode

Add to eleventy.

Add <meta name="generator" content="Eleventy"> to head

Once fully migrated to Netlify and ready for launch, make the gh-pages a redirect to the new domain

When 11ty v2 is more stable, use edge functions

Docs:

• https://www.learnwithjason.dev/blog/css-color-theme-switcher-no-flash
• https://docs.netlify.com/edge-functions/overview/
• https://www.11ty.dev/blog/eleventy-edge/

Maybe once a user makes N number of transliteration (~15–20), have a modal for feedback. Capture:

• level of satisfaction
• feedback
• email?

If dismissed, capture dismissed data like user agent, location, etc.

If the user does not support the necessary regex, add a call to server less function to spin it up. Add something into session storage so they don’t make unnecessary calls on every page load