Re: [Rule-www] RULE call for:db, downloads, translations

[Martin Stricker]

Marco Fioretti wrote:

> In the meantime, however, I could really use some assistance, first
> of all in translations, then, about point 2:

I'll do the German translation as soon as I can get to it.

>         (everybody) restoring the app_db database: it must be

Sorry, no PHP experience, only Perl.

>         (Benoit if still around and interested, everybody else
>         otherwise)
>                     move the "test PC" stuff (table, entry form...)
>                     to corresponding tables in the database

Suggested database design: Two tables, "test_pc" and "test_report". The
first gets it's primary key out of a sequence (AUTO_INCREMENT), all the
fields on the test PC entry form gets a column in this table.
"test_report" gets also an AUTO_INCREMENT primary key, then as a foreign
key the id of the test PC (from the other table) and a CLOB column for
the test report. Maybe add some other fields like installer
(slinky/miniconda) used, version of installer used, success of
installation... Sorry, the PHP code needs to be done by someone else.

>         Michael, could you suggest a standard/self maintaining way to
>         have the website always listing the latest miniconda/slinky
>         release available (something like php page listing the
>         /downloads directory all by itself)?

To list a directory's content in Perl:
print join('<BR>',`ls $directory`);
Perl has the nice backticks just like shells. I believe PHP can do
something similar.

> P.S.: HOW TO build/show multilingual site one piece at a time:
>         EX for spanish:
> 
>         populate www.rule-project.org/sp/ with empty php files having
>         the same names of those in www.rule-project.org/en/

Please not empty, but "Sorry, but this page has not been translated yet,
please see the <link>English version</link>. If you can provide a
translation, please look on our <link>how to translate for RULE</link>
page, thanks!" If possible, in the target language as well...

>         whenever a translation exists, empty file is substituted with
>         real one

Please make a template of the translation file as php.txt (so it will be
displayed instead of being processed) available, best linked on the "how
to translate for RULE" page which I ask you to create. Thanks!

>         desired language is passed around like this: index.php?L=sp
>         so that:
>                 if real sp/index.php exists it is shown, otherwise
>                 its empty placeholder redirects to en/index.php?L=sp

Spoke too soon... ;-)) But they should still get a request to help with
the translation!

>                 en/index.php sets all its internal links to the /sp
>                 directory, and the game repeats...

That's definitely the way to go! Good Idea(TM)!

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Linux Migration Project: http://www.linux-migration.org/
Red Hat Linux 7.3 for low memory: http://www.rule-project.org/
Registered Linux user #210635: http://counter.li.org/