<br><br>
<div><span class="gmail_quote">On 9/3/05, <b class="gmail_sendername">Mohammad Ghoniem</b> <<a href="mailto:Mohammad.Ghoniem@univ-ubs.fr">Mohammad.Ghoniem@univ-ubs.fr</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Salāms,<br><br>We need to decide how the data will be stored in the database. I can<br>imagine two scenarios :
<br>1- keep each po file as is i.e. in one big chunck corresponding to one<br>record in the database.</blockquote>
<div> </div>
<div>NOOOOOOOOO.. i don't prefer it in this way.. we once load the important data into db.. or each time we update the PO files from CVS.. update PO files with the approved string only!!</div>
<div>What left is db transcation.. each modification on a string in any PO file that will add a new record in db table</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">2- split po files and have one record per message.</blockquote>
<div> </div>
<div>YEs that's what i did.. </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">In all cases, we should make the choices explicit and draw a database<br>specification.<br><br>If each po file is stored in one chunk, we need a parser like the one I
<br>proposed lately to load the data into objects, before we can push the<br>data in some web form for the translators to deal with.</blockquote>
<div> </div>
<div>Yes sure we need a parser to extract the data from PO file and put it into one of db table.. that's has nothing to do with either u save the whole file as chunk data; CBlob or text or whatever datatype or each string as a single record in the table..
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> Once the<br>translator is done, we need to rebuild the po file before storing it in<br>the databse again. Some work is still needed here.
</blockquote>
<div> </div>
<div>NO... what's the use of the db then if we r going to update the files again.. the db is the intermediate layer here.. we need it to hold all the transaction the translators already did.. and keep them into db till the maintainer decide which is going to stay 'Approved' and which will be discarded and deleted from db..
</div>
<div>So when we should compile the PO file again.. that's one of the system admin roles.. each meanwhile.. he compiles the file.. so what will happened?! we will go through the db table and pickup only the approved strings and update them at their correct position in the PO file..
</div>
<div> </div>
<div>My point is that we dont' parse the file each time the translator modifying a string or reflect the translation change in PO file not before an approval from the maintainer side! in between will be db transaction..
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> I am not sure why<br>Maha you suggested to have a numerical identifier for each message. Is<br>this really necessary ?
</blockquote>
<div> </div>
<div>You mean the primary key or the order of the string is also unique numeric value..</div>
<div>the order string we will use it when we compile the approved string and put them in the right place at the file.. what's why we need it to put it in the first place while we parse the file... </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">In the web form, some data must be editable (msgstr) while some need not<br>(msgid and file header).</blockquote>
<div> </div>
<div>Yes?! didn't get ur point..</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Salām<br><br>Mohammad<br><br>--<br>Fedora-trans-ar mailing list<br><a href="mailto:Fedora-trans-ar@redhat.com">
Fedora-trans-ar@redhat.com</a><br><a href="http://www.redhat.com/mailman/listinfo/fedora-trans-ar">http://www.redhat.com/mailman/listinfo/fedora-trans-ar</a><br></blockquote></div><br>