diff options
Diffstat (limited to 'tde-i18n-ro/messages')
-rw-r--r-- | tde-i18n-ro/messages/tdegames/kgoldrunner.po | 32 | ||||
-rw-r--r-- | tde-i18n-ro/messages/tdepim/kmail.po | 94 |
2 files changed, 104 insertions, 22 deletions
diff --git a/tde-i18n-ro/messages/tdegames/kgoldrunner.po b/tde-i18n-ro/messages/tdegames/kgoldrunner.po index ac6cbfe4aca..d5aed32d82e 100644 --- a/tde-i18n-ro/messages/tdegames/kgoldrunner.po +++ b/tde-i18n-ro/messages/tdegames/kgoldrunner.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: @PACKAGE\n" -"POT-Creation-Date: 2020-05-11 04:09+0200\n" +"POT-Creation-Date: 2022-07-19 18:18+0000\n" "PO-Revision-Date: 2003-11-08 19:05+0200\n" "Last-Translator: Claudiu Costin <claudiuc@kde.org>\n" "Language-Team: Romanian <ro-kde@egroups.com>\n" @@ -42,8 +42,8 @@ msgid "" "next level. A hidden ladder will appear as you collect the last nugget.\n" "\n" "The hero (the green figure) is your deputy. To collect the nuggets, just " -"point the mouse where you want him to go. At first gravity takes over and " -"he falls ..." +"point the mouse where you want the hero to go. At first gravity takes over " +"and the hero falls ..." msgstr "" #: data_messages.cpp:36 @@ -55,7 +55,7 @@ msgid "" "This is an exercise in moving around. Follow the track of gold nuggets " "until the ladder pops up at the right. The hero can only follow the mouse " "along simple paths (like _ | L or U), so be careful not to get too far ahead " -"of him.\n" +"of them.\n" "\n" "DANGER: Try not to fall off the ladder or bar into the concrete pit at the " "bottom right. If you do get trapped there, the only way out is to kill the " @@ -70,8 +70,8 @@ msgstr "" msgid "" "Now you have to dig to get the gold! Just use the left and right mouse " "buttons to dig left or right of the hero's position. The hero can then jump " -"into and through the hole he has dug. He can also dig several holes in a " -"row and run sideways through the dug holes. Be careful though. After a " +"into and through the hole they have dug. They can also dig several holes in " +"a row and run sideways through the dug holes. Be careful though. After a " "while the holes close up and you can get trapped and killed.\n" "\n" "In the third box down, you have to dig two holes, jump in and quickly dig " @@ -96,14 +96,14 @@ msgid "" "You can handle enemies by running away, digging a hole or luring them into " "part of the playing area where they get stranded.\n" "\n" -"If an enemy falls into a hole, he gives up any gold he is carrying, then " -"gets stuck in the hole for a time and climbs out. If the hole closes while " -"he is in it, he dies and reappears somewhere else on the screen. You can " +"If an enemy falls into a hole, they give up any gold they are carrying, then " +"get stuck in the hole for a time and climb out. If the hole closes while " +"they are in it, they die and reappear somewhere else on the screen. You can " "deliberately kill enemies by digging several holes in a row.\n" "\n" "More importantly, you can run over an enemy's head. You must do that right " -"at the start of this level. Dig a hole, trap the enemy, wait for him to " -"fall all the way in, then run over him, with the other enemy in hot " +"at the start of this level. Dig a hole, trap the enemy, wait for them to " +"fall all the way in, then run over them, with the other enemy in hot " "pursuit..." msgstr "" @@ -153,9 +153,9 @@ msgid "" "There's nowhere to dig, so you must dodge the enemies and avoid falling to " "the concrete at the wrong time. Try to keep the enemies together.\n" "\n" -"If an enemy has a gold outline, he is holding a nugget. He might drop it as " -"he runs over the concrete or maybe at the top of a ladder ...... patience, " -"patience !!" +"If an enemy has a gold outline, they are holding a nugget. They might drop " +"it as they run over the concrete or maybe at the top of a ladder ...... " +"patience, patience !!" msgstr "" #: data_messages.cpp:89 @@ -180,9 +180,9 @@ msgid "" "It is best not to kill the enemy. Try it and you will find out why ... Heh, " "heh, heh !! ... ;-)\n" "\n" -"If you do kill him unintentionally, before you have collected the gold at " +"If you do kill them unintentionally, before you have collected the gold at " "the top left, you can still finish the level by digging away the side of the " -"pit he is in." +"pit they are in." msgstr "" #: data_messages.cpp:103 diff --git a/tde-i18n-ro/messages/tdepim/kmail.po b/tde-i18n-ro/messages/tdepim/kmail.po index 43dd8781daf..4a2a21cadc3 100644 --- a/tde-i18n-ro/messages/tdepim/kmail.po +++ b/tde-i18n-ro/messages/tdepim/kmail.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: kmail\n" -"POT-Creation-Date: 2022-04-06 20:16+0000\n" +"POT-Creation-Date: 2022-07-19 20:15+0000\n" "PO-Revision-Date: 2005-06-25 01:38+0300\n" "Last-Translator: Claudiu Costin <claudiuc@kde.org>\n" "Language-Team: Romanian <kde-i18n-ro@kde.org>\n" @@ -2406,12 +2406,13 @@ msgstr "" "puteţi activa, dar trebuie să aveţi grijă la consecinţele posibile.</p></qt>" #: configuredialog.cpp:3767 +#, fuzzy msgid "" "<qt><h3>Message Disposition Notification Policy</h3><p>MDNs are a " "generalization of what is commonly called <b>read receipt</b>. The message " "author requests a disposition notification to be sent and the receiver's " "mail program generates a reply from which the author can learn what happened " -"to his message. Common disposition types include <b>displayed</b> (i.e. " +"to their message. Common disposition types include <b>displayed</b> (i.e. " "read), <b>deleted</b> and <b>dispatched</b> (e.g. forwarded).</p><p>The " "following options are available to control KMail's sending of MDNs:</" "p><ul><li><em>Ignore</em>: Ignores any request for disposition " @@ -2421,7 +2422,7 @@ msgid "" "or ignoring them for others.</li><li><em>Deny</em>: Always sends a " "<b>denied</b> notification. This is only <em>slightly</em> better than " "always sending MDNs. The author will still know that the messages has been " -"acted upon, he just cannot tell whether it was deleted or read etc.</" +"acted upon, they just cannot tell whether it was deleted or read etc.</" "li><li><em>Always send</em>: Always sends the requested disposition " "notification. That means that the author of the message gets to know when " "the message was acted upon and, in addition, what happened to it (displayed, " @@ -7711,15 +7712,16 @@ msgid "Generate free/&busy and activate alarms for:" msgstr "Generează liber/&ocupat şi activează alarmele pentru:" #: kmfolderdia.cpp:539 +#, fuzzy msgid "" "This setting defines which users sharing this folder should get \"busy\" " "periods in their freebusy lists and should see the alarms for the events or " "tasks in this folder. The setting applies to Calendar and Task folders only " "(for tasks, this setting is only used for alarms).\n" "\n" -"Example use cases: if the boss shares a folder with his secretary, only the " -"boss should be marked as busy for his meetings, so he should select \"Admins" -"\", since the secretary has no admin rights on the folder.\n" +"Example use cases: if the boss shares a folder with their secretary, only " +"the boss should be marked as busy for their meetings, so they should select " +"\"Admins\", since the secretary has no admin rights on the folder.\n" "On the other hand if a working group shares a Calendar for group meetings, " "all readers of the folders should be marked as busy for meetings.\n" "A company-wide folder with optional events in it would use \"Nobody\" since " @@ -15247,3 +15249,83 @@ msgstr "" #~ msgid "Import mail from Evolution 2.x, Opera and Thunderbird" #~ msgstr "Importare mesaje din Evolution 2.x, Opera şi Thunderbird" + +#~ msgid "" +#~ "<qt><h3>Message Disposition Notification Policy</h3><p>MDNs are a " +#~ "generalization of what is commonly called <b>read receipt</b>. The " +#~ "message author requests a disposition notification to be sent and the " +#~ "receiver's mail program generates a reply from which the author can learn " +#~ "what happened to his message. Common disposition types include " +#~ "<b>displayed</b> (i.e. read), <b>deleted</b> and <b>dispatched</b> (e.g. " +#~ "forwarded).</p><p>The following options are available to control KMail's " +#~ "sending of MDNs:</p><ul><li><em>Ignore</em>: Ignores any request for " +#~ "disposition notifications. No MDN will ever be sent automatically " +#~ "(recommended).</li><li><em>Ask</em>: Answers requests only after asking " +#~ "the user for permission. This way, you can send MDNs for selected " +#~ "messages while denying or ignoring them for others.</li><li><em>Deny</" +#~ "em>: Always sends a <b>denied</b> notification. This is only " +#~ "<em>slightly</em> better than always sending MDNs. The author will still " +#~ "know that the messages has been acted upon, he just cannot tell whether " +#~ "it was deleted or read etc.</li><li><em>Always send</em>: Always sends " +#~ "the requested disposition notification. That means that the author of the " +#~ "message gets to know when the message was acted upon and, in addition, " +#~ "what happened to it (displayed, deleted, etc.). This option is strongly " +#~ "discouraged, but since it makes much sense e.g. for customer relationship " +#~ "management, it has been made available.</li></ul></qt>" +#~ msgstr "" +#~ "<qt><h3>Politică notificare prelucrare mesaj</h3><p>MDN-urile (Message " +#~ "Disposition Notification) reprezintă o generalizare a ceea ce este de " +#~ "obicei numit <b>confirmare de citire</b>. Autorul cere ca o notificare a " +#~ "prelucrării mesajului să-i fie trimisă şi programul de mail al " +#~ "destinatarului va genera un răspuns din care autorul poate să afle ce s-a " +#~ "întîmplat cu mesajul lui. Tipurile de prelucrare cele mai cunoscute sînt: " +#~ "<b>afişare</b> (adică citire), <b>ştergere</b> şi <b>răspîndire</b> (de " +#~ "exemplu mesajul a fost înaintat către altcineva).</p><p>Pentru a controla " +#~ "trimiterea MDN-urilor de către KMail, aveţi la dispoziţie următoarele " +#~ "opţiuni:</p><ul><li><em>Ignoră</em>: Ignoră orice cerere de notificare a " +#~ "prelucrării. Nu va fi trimis nici un MDN automat (recomandat).</" +#~ "li><li><em>Întreabă</em>: Răspunde la cereri numai după ce cere " +#~ "permisiunea utilizatorului. În acest fel puteţi trimite MDN-uri pentru " +#~ "mesajele selectate, iar pentru altele să ignoraţi sau să refuzaţi.</" +#~ "li><li><em>Refuză</em>: Întotdeauna trimite notificarea <b>refuzat</b>. " +#~ "Această metodă este numai <em>cu un pic</em> mai bună decît cea în care " +#~ "trimiteţi întotdeauna MDN-uri. Autorul va şti că mesajele au fost " +#~ "prelucrate, dar nu poate să afle dacă au fost citite sau şterse etc.</" +#~ "li><li><em>Trimite întotdeauna</em>: Trimite întotdeauna notificarea de " +#~ "primire cerută. Asta înseamnă că autorul mesajului va afla cînd a fost " +#~ "prelucrat mesajul şi în plus ce s-a întîmplat cu el (afişat, şters, " +#~ "etc.). Folosirea acestei opţiuni este puternic descurajată, dar a fost " +#~ "pusă la dispoziţie deoarece are sens pentru administrarea relaţiilor cu " +#~ "clienţii.</li> </ul></qt>" + +#~ msgid "" +#~ "This setting defines which users sharing this folder should get \"busy\" " +#~ "periods in their freebusy lists and should see the alarms for the events " +#~ "or tasks in this folder. The setting applies to Calendar and Task folders " +#~ "only (for tasks, this setting is only used for alarms).\n" +#~ "\n" +#~ "Example use cases: if the boss shares a folder with his secretary, only " +#~ "the boss should be marked as busy for his meetings, so he should select " +#~ "\"Admins\", since the secretary has no admin rights on the folder.\n" +#~ "On the other hand if a working group shares a Calendar for group " +#~ "meetings, all readers of the folders should be marked as busy for " +#~ "meetings.\n" +#~ "A company-wide folder with optional events in it would use \"Nobody\" " +#~ "since it is not known who will go to those events." +#~ msgstr "" +#~ "Această setare defineşte care din utilizatorii care partajează acest " +#~ "folder vor primi perioade \"ocupate\" în listele lor liber-ocupat şi vor " +#~ "vedea alarmele pentru evenimentele sau activităţile din acest folder. " +#~ "Această setare se aplică numai folderelor Calendar şi Activităţi (pentru " +#~ "activităţi, această setare este utilizată numai la alarme).\n" +#~ "\n" +#~ "Exemple de utilizări: dacă şeful partajează un folder cu secretara lui, " +#~ "numai şeful va fi marcat ca ocupat pentru şedinţe. El trebuie să " +#~ "selecteze \"Administratori\" deoarece secretara nu are permisiuni de " +#~ "administrare pentru folder.\n" +#~ "Pe de altă parte, dacă un grup de lucru partajează un Calendar pentru " +#~ "şedinţele de grup, toţi cei care pot citi folderul ar trebui marcaţi ca " +#~ "ocupaţi la şedinţe.\n" +#~ "Un folder la nivel de firmă cu evenimente opţionale în el va trebuie să " +#~ "folosească \"Nimeni\" deoarece nu se ştie cine va veni la acele " +#~ "evenimente." |