ويكي عربآيز - مساهمات المستخدم [ar]

نقاش:Semantic Arabic Encoding and Format

2007-10-11T11:10:42Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
This suggestions was posted by [[مستخدم:د.عمرو|Amru Gameel]] 07:43, 9 يوليو 2007 (PDT)
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر"
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
"خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bit space needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been fully discussed and there have been no suggestions on how to implement it. ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
===Comments===
Dr. Amru's ideas are very smart. They will be very useful in production systems. -[[مستخدم:Youssef Chahibi|يوسف]] 04:47, 10 يوليو 2007 (PDT)

There was a subproject dealing with how to classify verbs that might be of help. Check [http://lists.arabeyes.org/archives/general/2007/April/msg00000.html this] archived message from the Arabeyes General List.
==Reviewing The Suggestion==
===Some Thoughts===
Having reviewed my suggestion again, I realized the problem is really the input of Arabic text itself. The focus on correcting the encoding scheme was not correct. Using my encoding scheme brings in a few problems as well, and we already neglect ''tashkeel'' enough without the ability to have multiple short vowels on one letter. The same is true, to a lesser extent, for diacritic markers. At any rate, the input problem is not the problem with the encoding in the first place. [[مستخدم:د.عمرو|د.عمرو]] 09:05, 11 يوليو 2007 (PDT)
===Comments===
I think the problem in the first place is the fonts technology itself, which haven never been able to meet the demands of the Arabic language's script in general. Even OpenType, and the majority of contemporary technological innovations with font, are not really changing anything. [http://scripts.sil.org/RenderingGraphite Rendering Graphite], however, looks to be a promising free technology that is currently being developed. [[مستخدم:Hosny|خالد حسني]] 10:39, 13 يوليو 2007 (PDT)
==Notes Concerning the Suggestions==
Thanks Doctor Amru. I am sorry for the long delay in my response, but I wanted to review everything thoroughly. It is important that you, and all other contributors, supporters, and those just plain interested in the project realize the semantic component. The word level distinction here is very important because the derivational word structure of Arabic, which in turn influences morphology like ''tashkeel'' that represents its grammar, is the focal point of the system. I want to make full advantage of such an organizational principle in linguistics. The bottom line here is that form and function are linked in Semitic languages. This means that the focus should be a) Arabic (not languages with Arabic script that do not have the same grammatical paradigm like Urdu, Farsi, etc.), and b) the relationship between form and function. These suggestions steer away from the function (syntax, semantics, etc.) and focus on the form (morphology).
==Extending the Short Vowelling==
If we really wanted to improve upon the suggested encoding system for Arabic, it would make sense to get rid of the short vowels completely, and extend them. This means that the encoding will treat them like long vowels where ''alif'' equals ''fatha'', ''waaw'' equals ''damma'', and ''ya'a'' equals ''kesra''. If we look at it like this there is no need to encode the ''sukoon'' because it is merely the absence of a short vowel.

So, this means that there will only be seven potential values for the ''harakaat'', with the long vowels and short vowels becoming equal in the encoding as vowelling, and not separate entities that waste bit space for redundant components of Arabic morphology. This also comes back to the issue of the [[duality of the ''alif' and the ''hamza'']].

I think the remaining bits should be used to encode information about the ''tanween'' and the ''sheddah''. This allows for a spell checker to work on areas never previously covered, such as automatic correction of sun and moon letters, unnecessary nunation and extension of short vowels, so on and so forth.

There are also seem to be a lot of diffuse ideas here. A MediaWiki discussion page might not be the best place for this discussion. Keep in mint that we are in the process of [[Website_Revamp|revamping the website]].
[[مستخدم:عمرو غربية|Amru Gharbiyya]] 06:53, 5 سبتمبر 2007 (PDT)

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:47:22Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
This suggestions was posted by [[مستخدم:د.عمرو|Amru Gameel]] 07:43, 9 يوليو 2007 (PDT)
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر"
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
"خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been fully discussed and there have been no suggestions on how to implement it. ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
===Comments===
Dr. Amru's ideas are very smart. They will be very useful in production systems. -[[مستخدم:Youssef Chahibi|يوسف]] 04:47, 10 يوليو 2007 (PDT)

There was a subproject dealing with how to classify verbs that might be of help. Check [http://lists.arabeyes.org/archives/general/2007/April/msg00000.html this] archived message from the Arabeyes General List.
==Reviewing The Suggestion==
===Some Thoughts===
Having reviewed my suggestion again, I realized the problem is really the input of Arabic text itself. The focus on correcting the encoding scheme was not correct. Using my encoding scheme brings in a few problems as well, and we already neglect ''tashkeel'' enough without the ability to have multiple short vowels on one letter. The same is true, to a lesser extent, for diacritic markers. At any rate, the input problem is not the problem with the encoding in the first place. [[مستخدم:د.عمرو|د.عمرو]] 09:05, 11 يوليو 2007 (PDT)
===Comments===
I think the problem in the first place is the fonts technology itself, which haven never been able to meet the demands of the Arabic language's script in general. Even OpenType, and the majority of contemporary technological innovations with font, are not really changing anything. [http://scripts.sil.org/RenderingGraphite Rendering Graphite], however, looks to be a promising free technology that is currently being developed. [[مستخدم:Hosny|خالد حسني]] 10:39, 13 يوليو 2007 (PDT)
==Notes Concerning the Suggestions==
Thanks Doctor Amru. I am sorry for the long delay in my response, but I wanted to review everything throughly. It is important that you, and all other contributors, supports, and those just plain interest in the project realize the semantic component. The word level distinction here is very important because the derivational word structure of Arabic, which in turn influences morphology like ''tashkeel'' that represents its grammar, is the focal point of the system. I want to make full advantage of such an organizational principle in linguistics. The bottom line here is that form and function are linked in Semitic languages. This means that the focus should be Arabic (not languages with Arabic script that do not have the same grammatical paradigm), and the relationship between form and function. These suggestions steer away from the function (syntax, semantics, etc.) and focus on the form (morphology).
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:39:32Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
This suggestions was posted by [[مستخدم:د.عمرو|Amru Gameel]] 07:43, 9 يوليو 2007 (PDT)
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر"
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
"خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been fully discussed and there have been no suggestions on how to implement it. ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
===Comments===
Dr. Amru's ideas are very smart. They will be very useful in production systems. -[[مستخدم:Youssef Chahibi|يوسف]] 04:47, 10 يوليو 2007 (PDT)

There was a subproject dealing with how to classify verbs that might be of help. Check [http://lists.arabeyes.org/archives/general/2007/April/msg00000.html this] archived message from the Arabeyes General List.
==Reviewing The Suggestion==
===Some Thoughts===
Having reviewed my suggestion again, I realized the problem is really the input of Arabic text itself. The focus on correcting the encoding scheme was not correct. Using my encoding scheme brings in a few problems as well, and we already neglect ''tashkeel'' enough without the ability to have multiple short vowels on one letter. The same is true, to a lesser extent, for diacritic markers. At any rate, the input problem is not the problem with the encoding in the first place. [[مستخدم:د.عمرو|د.عمرو]] 09:05, 11 يوليو 2007 (PDT)
===Comments===
I think the problem in the first place is the fonts technology itself, which haven never been able to meet the demands of the Arabic language's script in general. Even OpenType, and the majority of contemporary technological innovations with font, are not really changing anything. [http://scripts.sil.org/RenderingGraphite Rendering Graphite], however, looks to be a promising free technology that is currently being developed. [[مستخدم:Hosny|خالد حسني]] 10:39, 13 يوليو 2007 (PDT)
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:27:35Z

Alharaka:

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:22:14Z

Alharaka:

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:17:00Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
"خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been fully discussed and there have been no suggestions on how to implement it. ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:13:41Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
"خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been discussed and no suggestion has been made on how to implement it.

** ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:12:58Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
"الاستخدام المتكرر
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
ب "خدم/6ال كرر/5م"
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been discussed and no suggestion has been made on how to implement it.

** ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T10:11:37Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:

* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
Although there are many good uses for the proposed encoding, it also has several problems:

* There will be tripartite input process. This means the user will have to input 1) the bare letter 2) the diacritic marker (if necessary) 3) the ''tashkeel'' vowel (if applicable).
* Foreign character input (e.g. numbers, symbols, English alphabet) has not been discussed and no suggestion has been made on how to implement it.

** ''The simple solution here is pretty simple, just designate the first four bits to encoding whether it is an Arabic letter or something else, as long as we can agree upon an encoding scheme for the different situations that might arise.''
* This is trying to reinvent the wheel, as the expression goes in English. Why should we? If this proposed encoding is really successful and beneficial for everyone, it is possible we can have it added to Unicode or have Unicode modified to include our ideas on the matter.
===What Is Wrong with Unicode?===
What is wrong with Unicode exactly?
* [http://www.unicode.org Official Unicode Homepage]
* [http://www.unicode.org/charts/ Index of Unicode Character Charts]
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:56:18Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Pros of the New Encoding===
There are several benefits to this new encoding:
* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field.
* Although they are linked, the letters and grammatical vowelling are still separate. This means it will be possible to have bare forms, without any diacritic markers. These bare forms could be extremely useful.
* This allows for the possibility of automatic vowelling systems that will take a text that the user inputted and vowel it for him or her completely.
* There is limitless potential for the new characters and bare forms, for instance, allowing all short vowels above or underneath a single character. These new characters and their derivatives can have very useful applications.
===Cons the New Encoding===
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:50:25Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

The idea here is that we are focusing on the naked letter, which means no diacritic markers (e.g. the technical name for the dots you see above certain Arabic letters). So the possible letters are as follows:

The Basic Alphabet in the Encoding:
<pre>
ا ب ح د ر س ص ط ع ف ك ل م ن ه null
</pre>

If you ignore the dot underneath the dot underneath the ba'a (as if it were a base form for ''ba'a'', ''ta'a'', and ''tha'a''), then you will see that the other divisions of the encoding will add the diacritics, grammatical vowelling (''tashkeel''), so on and so forth.

A more thorough explanation of this proposed encoding is to follow.
===Benefits of the New Encoding===
There are several benefits to this new encoding:
* The grammatical vowelling (''tashkeel'') is linked directly to the letter and therefore independent letters are not permissible. This is truer to the combination of morphology and syntax in the original Arabic script.
* This leads to the added bonus of reducing bitspace needed for the field. Consider the following:
<pre>
ص "بِسْمِ اللّهِ الرَّحْمَنِ الرَّحِيمِ
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:32:21Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology to the point that the way it is read and the way it is encoded become separate. The average user tends to write a given Arabic word as it is read. Consider the following examples:

Original Arabic, the way the user reads and writes:
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
Thus, this will only lead to a new problem, text input. This format means that we need another program that will properly understand the input in such a format. This problem will become even more complex if the user tries to input a word from an unknown verbal root form into the text. This is ignoring the different lexicons for the different varieties of Arabic, from Classical to Modern Standard to dialectical Arabic. We do not have the ability to make such large and complex dictionaries.
===So Where Do We Go From Here?===
Instead of looking at the encoding system at the lexical (e.g. word) level, we should look at it according to the letters in the word. The following picture will illustrate the improved encoding system:

[[صورة:ar_new_encoding_diagram.gif]]

Hopefully, this encodes correctly now.
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:22:48Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology in a way that the way it is read and the way it is written become totally separate. For instance, the first example will be written and encoded into the second example:

Original Arabic
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
I wonder if this work if I at least have text under here.
==Extending the Short Vowelling==
I would hope so.

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:22:06Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology in a way that the way it is read and the way it is written become totally separate. For instance, the first example will be written and encoded into the second example:

Original Arabic
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:21:28Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology in a way that the way it is read and the way it is written become totally separate. For instance, the first example will be written and encoded into the second example:

Original Arabic
<pre>
Insert Arabic example 1 here.
</pre>

Arabic via the Tarmeez Semantic Arabic Encoding Format:
<pre>
Insert Arabic example 2 here.
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
==Extending the Short Vowelling==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:19:42Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology in a way that the way it is read and the way it is written become totally separate. For instance, the first example will be written and encoded into the second example:

<pre>
Insert Arabic here.
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:10:17Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
===A Quick Overview of the Problem===
After reviewing the page here, one user suggested that this encoding will not solve the problem, but just lead to a new problem altogether. This encoding system tries to separate morphology in a way that the way it is read and the way it is written become totally separate. For instance, the first example will be written and encoded into the second example:

<pre>
Insert Arabic here.
</pre>
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
==Extending Short Vowelling==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T09:01:42Z

Alharaka:

<div dir="ltr" style="text-align: left" class="english">
==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
==Extending Short Vowelling==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T08:59:14Z

Alharaka:

==File Problems==
Currently, users are unable to access the zip file with the demo code [http://www.sinjab.com/TarmeezDemo0.1.zip here].
==The Basic Concept Needs Reviewing==
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
==Extending Short Vowelling==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T08:53:43Z

Alharaka:

==File Problems==
Currently, users are unable to access the zip file with the demo code [here|http://www.sinjab.com/TarmeezDemo0.1.zip].
==The Basic Concept Needs Reviewing==
==A Review of the Basic Concept==
==Notes Concerning the Suggestions==
==Extending Short Vowelling==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T08:52:26Z

Alharaka:

==File Problems==
Currently, users are unable to access the zip file with the demo code [here|http://www.sinjab.com/TarmeezDemo0.1.zip].
==The Basic Concept Needs Reviewing==
==A Review of the Basic Concept==
Notes Concerning the Suggestions====
==Extending the Short Vowels (الحركات)==

نقاش:Semantic Arabic Encoding and Format

2007-10-11T08:47:38Z

Alharaka:

==File Problems==
Currently, users are unable to access the zip file with the demo code [here|http://www.sinjab.com/TarmeezDemo0.1.zip].
==Header 2==
==Header 3==
==Header 4==

Semantic Arabic Encoding and Format

2007-09-26T02:38:15Z

Alharaka:

<div class=english>
{{Arabic|الترميز المعنوي للغة العربية}}
'''Semantic Arabic Encoding and Format'''

This information is intended to be a permanent exchange during the progression of the project. Any suggestions or contributions are welcome.

==First glance==

Computers still deal with the [[Arabic]] language in comparison to other languages, especially English, in a limited way. It will deal with it on the textual level, with regards to form, storage, [[encoding]] problems,or their treatment or with respect to meaning which is included in by the text. Moreover, the Arabic language, in contrast to European languages, is a heavily [[morphological language]] (i.e. there is a rigid structure that links the structure of words in relation to their semantic and logical meaning).

This should justify striving for the understanding of different mechanisms of the structure of the Arabic language from which it benefits and ending the pressing need for treating unstructured text and dealing with meaning in Arabic.

Currently, we are in need of a clear reading of texts on [[human pronunciation]], especially Arabic letters, to guarantee Semantic Arabic Encoding and Format's binary specs accurately whether they reflect human characteristics, acoustic characteristics, or that which is specific to the Arabic language in the way the letters follow each other or are grouped together in the hope that we may contribute to limited the total space it is necessary to study for this project.

Also, we need a chart of irregular words and loanwords in the Arabic language and irregular grammar rules. It appears that the Arab Translators Society is succeeding in this way as we too need to make up charts of derived patterns and devices for their classification and linking.

In the advanced stages, we will also need to round up all components of the word with the connected pronouns or even separated ones with genitive markers.

==Project Objectives==

The Arabic Semantic Encoding project aims to writing mechanisms for storing Arabic texts (words) including its structure and derivational relationships in a way that reflects the most of semantic correlation possible. These objectives include:

* The development of a system to include the meaning and the [[sentence structure]].
* The generation of an non-itemized Arabic [[morphological lexicon]] which will be the basis for a complete Arabic lexicon.
* Easing [[searching and categorization]] whether on the morphological or semantic level.
* The possibility for linking the encoding with components to form a [[spell checker]] and then a [[grammar checker]] (which is the first system we really wanted to develop, an interactive spell checker for simplifying writing in Modern Standard Arabic (Fusha), an effective dictionary for words and technical terms, etc.).
* The ability for the system to simplify dealing with Modern Standard Arabic (Fusha) and its writing accurately (to increase its use) and store texts to structure [[unstructured texts]], then find mechanisms for [[moving Arabic texts to a structured and correlated format]]. (Currently, less than 1% of Arabic texts are structured.)
* A way to distinguish non-Arabic words (i.e. not derived from Arabic or are not subject to Arabic structure) and putting it through a framework that must exist.
==The Current Idea for the Project==
ُAs far as I see it, this project depends upon breaking new ground on dealing with Arabic text as a series of utterances in an [[alphabetic encoding]] and dealing with [[word encoding]] at the alphabet level like a continuous classification device that resembles [[building a rule resolver]] with an attempt to preserve the authenticity of the the symbol throughout and simplifying dealing with it via [[high level programming languages]].
==Project Progress==
We have succeeded currently in our first rough sketch for project. We have written a preliminary outline for the [[Semantic Encoding and Format Project]] as written by Brother [[Khaldoun Sinjab]] as a simple prototype to clarify [[the basic idea behind the project]].
==What We Need==
*The [[vocal research]]

Semantic Arabic Encoding and Format

2007-09-26T02:37:48Z

Alharaka:

Semantic Arabic Encoding and Format

2007-09-26T02:36:53Z

Alharaka:

Semantic Arabic Encoding and Format

2007-09-26T02:35:43Z

Alharaka:

Semantic Arabic Encoding and Format

2007-09-26T01:43:28Z

Alharaka:

<div class=english>
{{Arabic|الترميز المعنوي للغة العربية}}
'''Semantic Arabic Encoding and Format'''

This information is intended to be a permanent exchange during the progression of the project. Any suggestions or contributions are welcome.

==First glance==

Computers still deal with the [[Arabic]] language in comparison to other languages, especially English, in a limited way. It will deal with it on the textual level, with regards to form, storage, [[encoding]] problems,or their treatment or with respect to meaning which is included in by the text. Moreover, the Arabic language, in contrast to European languages, is a heavily [[morphological language]] (i.e. there is a rigid structure that links the structure of words in relation to their semantic and logical meaning).

This should justify striving for the understanding of different mechanisms of the structure of the Arabic language from which it benefits and ending the pressing need for treating unstructured text and dealing with meaning in Arabic.

==Project Objectives==

The Arabic Semantic Encoding project aims to writing mechanisms for storing Arabic texts (words) including its structure and derivational relationships in a way that reflects the most of semantic correlation possible. These objectives include:

* The development of a system to include the meaning and the [[sentence structure]].
* The generation of an non-itemized Arabic [[morphological lexicon]] which will be the basis for a complete Arabic lexicon.
* Easing [[searching and categorization]] whether on the morphological or semantic level.
* The possibility for linking the encoding with components to form a [[spell checker]] and then a [[grammar checker]] (which is the first system we really wanted to develop, an interactive spell checker for simplifying writing in Modern Standard Arabic (Fusha), an effective dictionary for words and technical terms, etc.).
* The ability for the system to simplify dealing with Modern Standard Arabic (Fusha) and its writing accurately (to increase its use) and store texts to structure [[unstructured texts]], then find mechanisms for [[moving Arabic texts to a structured and correlated format]]. (Currently, less than 1% of Arabic texts are structured.)
* A way to distinguish non-Arabic words (i.e. not derived from Arabic or are not subject to Arabic structure) and putting it through a framework that must exist.
==The Current Idea for the Project==
ُAs far as I see it, this project depends upon breaking new ground on dealing with Arabic text as a series of utterances in an [[alphabetic encoding]] and dealing with [[word encoding]] at the alphabet level like a continuous classification device that resembles [[building a rule resolver]] with an attempt to preserve the authenticity of the the symbol throughout and simplifying dealing with it via [[high level programming languages]].
==Project Progress==
We have succeeded currently in our first rough sketch for project. We have written a preliminary outline for the [[Semantic Encoding and Format Project]] as written by Brother [[Khaldoun Sinjab]] as a simple prototype to clarify [[the basic idea behind the project]].
==What We Need==

*the [[vocal research]]

Semantic Arabic Encoding and Format

2007-03-16T15:56:14Z

Alharaka:

Semantic Arabic Encoding and Format

2007-03-16T14:36:40Z

Alharaka: