English Home Romanian Home
Electronic Bible Online Pages Multi Language Phone Application One Language d/">Download Ipod / MP4 Player Package Electronic Online Mobile Pages
Electronic Books Online Pages Build Ebook Phone Application Download Ebook Phone Application Download Desktop Application Download Ipod / MP4 Player Package Electronic Online Mobile Pages
Create Bible Application Create E-Books Application
Credits News
About our project   |    Mobile Pages   |   
Electronic Books / Adventist / Romanian_non-diacritics / Comentarii Biblice / Web / Geneza

Adventist

Romanian_non-diacritics

Printable ModePrintable Mode

Geneza 5:32


5:32 Noe, la varsta de cinci sute de ani, a nascut pe Sem, Ham si Iafet.

Noe, la varsta de cinci sute de ani. In ebraica aceasta expresie se citeste literal astfel: ,,Noe era un fiu a cinci sute de ani”, ceea ce inseamna ca el era in cel de-al cinci sutelea an al sau. In acel timp, ,,fiu al unui an” insemna, strict vorbind, in timpul primului an al vietii (Exod 12,5). Acest fapt, un punct important in limbajul cronologic ebraic devine si mai clar din comparatia versetelor 6 si 11 ale capitolului 7. Desi ambele versete vorbesc despre inceputul potopului, unul dintre ele declara ca Noe avea 600 de ani, iar celalalt spune ca evenimentul s-a intamplat in al sase sutelea an al lui Noe. Ca urmare a versetului precedent, ,,Noe era un fiu a sase sute de ani” inseamna ca el era in al sase sutelea an, si nu in al sase sutelea unu an, dupa cum, in mod firesc, am trage concluzia.

Nici unul dintre patriarhii de mai inainte nu a asteptat atat de multi ani inainte de nasterea urmasilor sai ca Noe; o jumatate de mileniu a trecut inainte ca propriul camin sa fie binecuvantat de sosirea unui fiu (vezi pag. 183). Aceasta genealogie se opreste la Noe, mentionand numai nasterea fiilor sai. Mentionarea tuturor celor trei fii prevesteste importanta lor in repopularea pamantului dupa potop.

A nascut pe Sem, Ham si Iafet. In legatura cu acesta fapt, trebuie sa fie explicat un alt principiu de genealogie ebraica. Din insiruirea numelor fiilor lui Noe redata aici si in alta parte, se poate ajunge la impresia ca Sem a fost cel mai in varsta, iar Iafet cel mai tanar dintre cei doi fii ai lui Noe. Acest lucru nu corespunde realitatii si se poate vedea din comparatia textului cu cateva alte texte. Fiii lui Noe nu erau fii gemeni (vezi cap. 9,24; 10,21). Conform capitolului 9,24, Ham a fost cel mai tanar dintre frati. Capitolul 10,21, de altfel, se refera fie la Sem, fie la Iafet ca ,,mai in varsta” din cei doi, desi ambigua constructie gramaticala ebraica nu lamureste care dintre cei doi era mai in varsta. Din capitolul 11,10 aflam ca Sem era in varsta de 100 de ani la doi ani dupa potop, cand tatal sau era in varsta de 602 ani. Prin urmare, varsta lui Noe la nasterea lui Sem trebuia sa fi fost de 502 ani – nu de cinci sute de ani asa cum se putea trage concluzia din cap. 5,32. Insa unul dintre cei trei, cel mai mare, s-a nascut in al cinci sutelea an al lui Noe (cap. 5,32). Aceste texte duc la concluzia ca, de fapt, Iafet a fost cel mai mare fiu al lui Noe, fiind nascut cand tatal sau era in varsta de 500 de ani, si ca Sem si Ham au urmat in aceasta ordine. De aceea, traducerea din KJV a capitolului 10,21 este corecta, mai degraba decat acea din RSV, din care rezulta ca Sem a fost fiul cel mai mare. Ultima parte a capitolului 5,32 ar fi fost redata mai bine astfel: ,,Si Noe a inceput sa nasca pe Iafet, Sem si Ham”.

Sem este mentionat ca fiind cel dintai dintre cei trei fii din cauza importantei lui ca stramos al liniei patriarhale de dupa potop, de unde urma sa iasa poporul ales al lui Dumnezeu impreuna cu samanta fagaduita. Ham este mentionat urmatorul ca stramos al neamurilor cu care cititorii Vechiului Testament din timpul lui Moise si mai tarziu au avut mai multe legaturi decat cu urmasii lui Iafet care locuiau in regiuni mai indepartate. Acelasi principiu este repetat si in cazul lui Avraam, unde el, care este cel mai mic dintre fiii lui Terah, este mentionat cel dintai (cap. 11,27) din cauza mai marii lui importante fata de cei pentru care a fost scris raportul.

Prin reducerea varstelor lui Iared, Metusala si Lameh la varsta nasterii fiilor lor intai nascuti, Pentateucul samaritean ingaduie intre creatiune si potop numai 1307 ani in loc de 1656 dupa cum este in textul ebraic si in traducerile engleze bazate pe el.

Dimpotriva, LXX prevede o perioada mult mai lunga inainte de potop. Ea face aceasta prin adaugarea unui secol in plus la varsta fiecaruia dintre primii cinci patriarhi si la aceea a lui Enoh la data nasterii fiilor lor intai nascuti si prin schimbari mai mici cu privire la alti doi. Ca urmare, ajunge la un total de 2242 sau 2262 de ani (diferite manuscrise arata o deosebire intre 167 si 187 pentru varsta lui Metusala la nasterea lui Lameh).

Cronologia antediluviana redata de Iosif Flavius este practic aceeasi cu cea din LXX, presupunandu-se ca a fost derivata din acea versiune, care circula in zilele lui. Iosif mentioneaza varsta lui Metusala ca fiind de 187 ani.

Daca cifra de 187 pentru Lameh este considerata corecta si nu cea de 167, atunci calculul este usor. Multi cititori nu sunt constienti de deosebirile din genealogiile antice, deoarece KJV si alte traduceri protestante se bazeaza pe textul ebraic.

Este interesant de observat ca lista din Geneza 5 raporteaza zece generatii cu varste indelungate, asemenea vechilor traditii Mesopotamiene care arata in mod precis zece generatii inainte de potop si lungimea vietii neamului de oameni in timpul acestei perioade. Lista babiloniana incepe cu observatia ca ,,suveranitatea a coborat din ceruri” si il prezinta pe Alulim, care insemna ,,om” ca stramos al neamului omenesc (compara cu ebraicul ’adam, ,,om”). Totusi, alte asemanari nu exista intre cele doua liste, nici de nume, nici ca perioade de timp. Vezi tabelul cronologiei cartii Geneza. Comentariile lui Ellen G. White

1-32 CH 19; PP 80-89; 3T 139

1,3 PP 80

3-8 SR 57

5 PP 82

5,8 3T 138

18-24 SR 57

21,22 GW 51; PP 84

21-24 8T 305, 329, 331

22 CT 487; Ev 78, 681; ML 8, 14, 98, 255; MM 124, 276; PP 92; SC 103; 2T 121; 3T 543; 4T 616; 5T 113, 535, 596

24 Ed 127; EW 40; GC 299; GW 254; MB 54; ML 341; PK 486; PP 87; SC 103; SR 59; TM 338, 388; 6T 392; 7T 155


Printable Mode

Seek to any passage:


Book:
Chapter:
Paragraph:

Search the text:


Search in:
Terms:
Case insensitive:


Special note for ANDROID SmartPhones
I recommend to download PhoneMe emulator for Android from here. Especially I recommend phoneME Advanced - Foundation Profile + MIDP High Resolution b168 rev20547 from here, or from here.

Then you have to build your application, to transfer the .jar and .jad files on your mobile phone and run using this nice emulator.

1. Install a Zip Utility from Android Market.

2. Install a File Manager from Android Market.

3. Download and install PhoneMe, as mentioned above.

4. Build your application by using Download Multilingual Service or Dynamic Download (zip).

5. Copy the zip file into your Android Phone and unzip the content in a folder, and then write down the path to the unzipped files and the name of the .jad file.

6. Launch PhoneMe from your smartphone.

7. Inside PhoneMe, write to the main window the path and the name to the .jad file, above mentioned. Will look something like: file:///mnt/sd/download/BiblePhone.jad and then press enter.

8. The application will be installed, and next a hyperlink will be available below the above mentioned textbox. On this way you can install as many of MIDP application you like on your Android Phone.


How to install the application in Java Mobile enabled phones

It is possible now to have the Holy Scriptures on your mobile phone and to read it wherever you are due to the Mobile Information Device Profile (MIDP) technology in 1.0 and 2.0 versions, developed for Java applications.

A good advice is to try in the beginning the MIDP 1.0 / 128 Kbytes version, and progressively to advance to MIDP 2.0 and larger volumes (512 Kbytes or more).

The application is available for MIDP 2.0, MIDP 1.0. You have only to select one table on the field MIDP2.0 or MIDP1.0, according to the desired Bible version. Then, you shall make a click on the JAR (Java Archive) file in order to obtain the software to be installed on your mobile phone.

I recommend you to start with STARTER(MIDP1.0old) edition, then to continue with INTERMEDIATE(MIDP1.0), and in the end, if the mobile phone supports this thing, to try to install the ADVANCED (MIDP2.0) edition. Also, start with 128 kbytes volumes, continue with 512 kbytes, and at the end try the version in one file.

There are cases where the mobile phone requires so called JAD (Java Descriptor) files. These JAD files has to be uploaded, on this case, together with the desired JAR files(s).

There are different methods to download the applications in your mobile phone as follows:
1. Directly from Internet by using a WAP or GPRS connection
2. By using the infrared port of the mobile phone
3. By wireless Bluetooth access to the mobile phone
4. By cable link between PC ad mobile phone
5. If none from the above cases are valid

Next, we shall examine each case in order to have a successfully installation of the software.


1. Directly from Internet by using a WAP or GPRS connection
 

If your have Internet access on your mobile phone (e.g. WAP or GPRS), it is enough to access https://biblephone.intercer.net/wap/  from the browser of the mobile phone, and to access the desired Bible version, and then to make an option about MIDP1.0 or MIDP2.0, and finally to select the desired module (e.g. one or more). After the last selection, the desired version will be downloaded on your mobile phone.

Many phones have only this option for installing JAVA appplications.

2. By using the infrared port of the mobile phone

Sometimes there is a need for a special uploader software for specific mobile phones.

If you don't have access to Internet directly from your mobile phone, then you shall have to pass to this step requiring to have infrared ports on your mobile phone and on the computer.
a. On this case, you will download the application by using the computer from the Internet (i.e. JAR files).
b. Once the application is downloaded (preferable on the desktop) you will have to activate the infrared port on the mobile phone and align it with the infrared port of the computer (preferable laptop).

c. Then a window will appear asking what file you want to send to the mobile phone. Next, you will select the downloaded JAR file, and after OK, the mobile phone will ask you if you want to load that file. You say YES and the application will be downloaded on your mobile phone.
d. Probably, you will be asked by the mobile phone where you want to save it (e.g. on the games or applications directories). After you made this selection, the file will be ready to be loaded for run.
The displaying preference can be set inside the application in order to have larger fonts, full screen display etc.

3. By wireless Bluetooth access to the mobile phone

Sometimes there is a need for a special uploader software for specific mobile phones.
This situation is similar with the infrared case. You have only to activate Bluetooth access on your mobile phone (check if exists) and on the computer (check if exists).

4. By cable link between PC ad mobile phone
Sometimes there is a need for a special uploader software for specific mobile phones.
On this case the steps are as follows:

a. On this case, you will download the application by using the computer from the Internet (i.e. JAR files).
b. Once the application is downloaded (preferable on the desktop) you will have to set up the wired connection between the mobile phone and the computer. Next, you will start the synchronization / data transfer application and download the JAR file in your mobile phone. Surely, you will have to consult the CD of your mobile phone.
c. By this application you shall transfer into your mobile phone the JAR file in the games or applications directories. Next, you will have to select for run the JAR desired file.

5. If none from the above cases are valid
On this unhappy case, I recommend you to find a friend with a laptop having infrared / Bluetooth capabilities, or to buy a data link cable, or to change your current model of mobile phone.
Unfortunately, some models of mobile phones require only WAP/GPRS in order to download and run Java applications.


Sometimes there is a need for a special uploader software for specific mobile phones. Therefore check the documentation of them and also the page for specific models.

Why so many versions? Simple, because not all the mobile phones support the Bible in one file with MIDP 2.0 (the most advanced for the time being).

Multilingual Online Ebooks

It is possible now to have the inspirational ebooks on your browser and to read it allowing you to make comparisons between different translations or versions for a specific language. This occasion is unique, and you have only to browse to the desired author and book.


Select another version:



Source: Text from read this link, compiled by biblephone2008@gmail.com





free counters

Locations of visitors to this page






If you have any questions, remarks, suggestions, please contact me here. May God bless you in studying the Holy Scriptures.



Sitemap: Please select the BiblePhone modules in your language: