[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Things to be done
- To: Development Discussions <developer at arabeyes dot org>
- Subject: Re: Things to be done
- From: Riyad Preukschas <rpreukschas at web dot de>
- Date: Wed, 25 Feb 2004 18:21:23 +0100
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Assalamu Alaikum,
That's fine if we have a lot (and I mean a LOT) of people willing to do
that, but it's simply a LOT of work.
I understand that it's a good idea to do this but do we really need it?
At least some of it. I would appreciate it a lot if there would be any
information about the author or the used source in that file.
Or at least:
- "version" and "lang" or "language" attributes
- separate sura name transliterations and translations (i.e. separate
"name" and "translation" attributes in a sura element).
- rename the ayat numbering attribute from "id" to something like "nr"
or "no", because it is confusing because the "id" attributes are meant
to be unique per file.
- recitation breakpoint indicators (U+06D6 to U+06DB)
I mean if it's an XSLT application, I would totally agree but it's not and
I don't mind postponing most of the functionality to the c/c++ code instead of
doing it in the XML file (especially if we are talking about the Qur'an).
I think indications for where ALLAH is referred to in the Quran text
belong into the file (especially because it differs in every source). Or
make the user know that the translator made a comment to a translated
piece of text.
That would make lef much harder for a newbie who want to play with the text
a bit.
But more useful for the user.
I don't think these files were meant for "playing with them a bit".
I think it's better for developers to have the possibility to provide as
much information about the source as possible.
I know we should protect the text with md5/gpg or whatever but that doesn't
mean that we shouldn't do anything else, I mean things like the number of verses
each chapter has and the places of sajda really needn't go to the XML file (again, since
we are not making a XSLT application).
I've never talked about the number of verse per chapter.
I thought of including the sajda element, because as far as i can
remember there are sajdas in the Quran which are not at the not at the
end of the ayat. So you can mark the passage where the sajda should be
done and not only the whole ayat.
Anyway, if you can come up with a much simpler XML structure that doesn't
need a lot of ork, I would appreciate it.
I did, but the things I mentioned at the top of this mail are still
included:
http://www.includeme.ma.cx/kuran/drafts/quran_2_sp_draft.xml
and if this is still too complex then look at this:
http://www.includeme.ma.cx/kuran/drafts/quran_2_rsp_draft.xml
Selam,
Riyad Preukschas