Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transcoding vowel-marker characters #78

Open
funderburkjim opened this issue Sep 28, 2024 · 7 comments
Open

Transcoding vowel-marker characters #78

funderburkjim opened this issue Sep 28, 2024 · 7 comments

Comments

@funderburkjim
Copy link
Contributor

In #76, @Andhrabharati proposes an extension to slp1 for representation of vowel-marker characters of Devanagari. Let's continue that discussion here.

@funderburkjim
Copy link
Contributor Author

In deva->slp1, how do we know when to insert the marker?
Also, how to type examples? I use pramukhime to type Devanagari.

@Andhrabharati
Copy link

Does opening the new issue and 'continuing the discussion' mean that the point has been accepted in principle?
[otherwise, no point spending time on this!]

@funderburkjim
Copy link
Contributor Author

point has been accepted in principle?

Not sure how to answer. Since the need for such an extension is rare in the current CDSL,
this issue is not pressing. However, I am curious to see whether the cdsl transcoding
scheme can be extended in the way suggested.

@Andhrabharati
Copy link

Andhrabharati commented Sep 30, 2024

This may be somewhat comparable with the jihvAmUlIya and upadhmAnIya characters that are rarely come across!!

@gasyoun
Copy link
Member

gasyoun commented Sep 30, 2024

Since the need for such an extension is rare in the current CDSL, this issue is not pressing.

agreee

funderburkjim added a commit that referenced this issue Oct 6, 2024
@funderburkjim
Copy link
Contributor Author

a first test

Work appears in issue78 directory.

There is no problem in extending slp1_deva1.xml to display the vowel-marker characters.
Compare test01_in.txt and test01_out.txt.

deva1_slp1.xml was extended in the most obvious way. Applying this to test01_out.txt yields
test01_in_out.txt, which is different from test01_in.txt.
Thus, invertibility fails for this version of deva1_slp1.xml

Recall that a transcoding file specifies a finite-state machine, which processes a text string.
The deva1_slp1.xml state machine has only one state (named INIT).

Thus, it's finite state machine does not distinguish the context of, for instance, \u093e (Devanagari Vowel Sign A); so it always generates the slp1 'A'.

Note that slp1_deva1.xml takes 2 states to generate Devanagari from slp1.
Perhaps a version of deva1_slp1.xml with 2 states could properly distinguish the context.

@gasyoun
Copy link
Member

gasyoun commented Oct 7, 2024

The deva1_slp1.xml state machine has only one state (named INIT).

Too abstract for me. For long time something I totally do not understand ))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants