www/gnu/po rms-lisp.sq.po

www-commits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/gnu/po rms-lisp.sq.po

From:	Besnik Bleta
Subject:	www/gnu/po rms-lisp.sq.po
Date:	Sat, 01 Jan 2011 23:08:07 +0000
CVSROOT:        /web/www
Module name:    www
Changes by:     Besnik Bleta <beso>     11/01/01 23:08:07

Added files:
        gnu/po         : rms-lisp.sq.po 

Log message:
        first draft

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.sq.po?cvsroot=www&rev=1.1

Patches:
Index: rms-lisp.sq.po
===================================================================
RCS file: rms-lisp.sq.po
diff -N rms-lisp.sq.po
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ rms-lisp.sq.po      1 Jan 2011 23:08:03 -0000       1.1
@@ -0,0 +1,279 @@
+# Translation into Albanian of minimial gnu.org site pages
+# Copyright (C) 2010Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
+# Besnik Bleta <address@hidden> 2010.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2009-08-06 04:25-0300\n"
+"PO-Revision-Date: 2011-01-02 01:10+0200\n"
+"Last-Translator: Besnik Bleta <address@hidden>\n"
+"Language-Team: Shqip <address@hidden>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+# type: Content of: <title>
+msgid "My Lisp Experiences and the Development of GNU Emacs - GNU Project - 
Free Software Foundation (FSF)"
+msgstr "PÃ«rvoja Ime Me Lisp dhe Zhvillimi i GNU Emacs - Projekti GNU - Free 
Software Foundation (FSF)"
+
+# type: Content of: <h2>
+msgid "My Lisp Experiences and the Development of GNU Emacs"
+msgstr "PÃ«rvoja ime me Lisp dhe Krijimi i GNU Emacs"
+
+# type: Content of: <h3>
+msgid "(Transcript of Richard Stallman's Speech, 28 Oct 2002, at the 
International Lisp Conference)."
+msgstr "(Transkriptim i FjalÃ«s sÃ« Richard Stallman-it, 28 Tetor 2002, nÃ« 
International Lisp Conference)."
+
+# type: Content of: <p>
+msgid "Since none of my usual speeches have anything to do with Lisp, none of 
them were appropriate for today. So I'm going to have to wing it.  Since I've 
done enough things in my career connected with Lisp I should be able to say 
something interesting."
+msgstr "NgaqÃ« asnjÃ« nga fjalimet e mia tÃ« zakonshme nuk lidhet gjÃ«kundi me 
Lisp-in, asnjÃ« prejt yre nuk qe i pÃ«rshtatshÃ«m pÃ«r sot. Ndaj do tÃ« mÃ« 
duhet tÃ« improvizoj.  NgaqÃ« gjatÃ« karierÃ«s time kam bÃ«rÃ« boll gjÃ«ra qÃ« 
lidhen me Lisp-in, do tÃ« duhej tÃ« isha nÃ« gjendje tÃ« them diÃ§ka 
interesante."
+
+# type: Content of: <p>
+msgid "My first experience with Lisp was when I read the Lisp 1.5 manual in 
high school. That's when I had my mind blown by the idea that there could be a 
computer language like that. The first time I had a chance to do anything with 
Lisp was when I was a freshman at Harvard and I wrote a Lisp interpreter for 
the <abbr title=\"Programmed Data Processor\">PDP</abbr>-11. It was a very 
small machine &mdash; it had something like 8k of memory &mdash; and I managed 
to write the interpreter in a thousand instructions. This gave me some room for 
a little bit of data. That was before I got to see what real software was like, 
that did real system jobs."
+msgstr "Takimi im i parÃ« me Lisp-in qe leximi i doracakut tÃ« Lisp 1.5 nÃ« 
shkollÃ«n e mesme. Kjo qe koha kur mÃ« iku mendja nga ideja qÃ« mund tÃ« kishte 
njÃ« gjuhÃ« kompjuteri si kjo. Hera e parÃ« qÃ« pata rastin tÃ« bÃ«j diÃ§ka me 
Lisp-in qe kur isha riosh nÃ« Harvard dhe shkruajta njÃ« interpretues Lisp pÃ«r 
<abbr title=\"Programmed Data Processor\">PDP</abbr>-11. Qe makinÃ« shumÃ« e 
vogÃ«l &mdash; kish a s'kish 8k kujtesÃ« &mdash; dhe ia dola tÃ« shkruaj 
interpretuesin brenda njÃ« mijÃ« udhÃ«zimesh. Kjo mÃ« la pak vend pÃ«r pakÃ«z 
tÃ« dhÃ«na. Kjo ndodhi pÃ«rpara se tÃ« arrija tÃ« shihja se Ã§farÃ« qe vÃ«rtet 
njÃ« <em>software</em>, ai qÃ« kryente detyra tÃ« vÃ«rteta nÃ« sistem."
+
+# type: Content of: <p>
+msgid "I began doing work on a real Lisp implementation with JonL White once I 
started working at <abbr title=\"Massachusetts Institute of 
Technology\">MIT</abbr>. I got hired at the Artificial Intelligence Lab not by 
JonL, but by Russ Noftsker, which was most ironic considering what was to come 
&mdash; he must have really regretted that day."
+msgstr "Zura tÃ« punoj pÃ«r njÃ« sendÃ«rtim tÃ« njÃ«mendtÃ« Lisp me JonL 
White-in sapo fillova tÃ« punoj nÃ« <abbr title=\"Massachusetts Institute of 
Technology\">MIT</abbr>. MÃ« punÃ«suan nÃ« Artificial Intelligence Lab, jo 
JonL-ja, por Russ Noftsker-i, Ã§ka qe mÃ« ironikja kur mendon se Ã§'do vinte 
mÃ« pas &mdash; vÃ«rtet duhet tÃ« jetÃ« penduar pÃ«r atÃ« ditÃ«."
+
+# type: Content of: <p>
+msgid "During the 1970s, before my life became politicized by horrible events, 
I was just going along making one extension after another for various programs, 
and most of them did not have anything to do with Lisp. But, along the way, I 
wrote a text editor, Emacs. The interesting idea about Emacs was that it had a 
programming language, and the user's editing commands would be written in that 
interpreted programming language, so that you could load new commands into your 
editor while you were editing. You could edit the programs you were using and 
then go on editing with them. So, we had a system that was useful for things 
other than programming, and yet you could program it while you were using it. I 
don't know if it was the first one of those, but it certainly was the first 
editor like that."
+msgstr "GjatÃ« viteve '70, pÃ«rpara se jeta ime tÃ« politizohej nga ngjarje 
tÃ« tmerrshme, thjesht e shtyja duke bÃ«rÃ« zgjerim pas zgjerimi pÃ«r programe 
tÃ« ndryshme, dhe shumica e tyre nuk kishin tÃ« bÃ«nin aspak me Lisp-in. Por, 
nÃ« rrugÃ« e sipÃ«r, shkrojta njÃ« pÃ«rpunues tekstesh, Emacs. Ideja 
interesante rreth Emacs-it qe qÃ« kish njÃ« gjuhÃ« programimi brenda, dhe qÃ« 
urdhrat e pÃ«rdoruesit pÃ«r pÃ«rpunime mund tÃ« shkruheshin nÃ« atÃ« gjuhÃ« tÃ« 
interpretuar programimesh, e kÃ«shtu mund tÃ« ngarkonit urdhra tÃ« reja te 
pÃ«rpunuesi juaj ndÃ«rkohÃ« qÃ« punonit me tÃ«. Mund tÃ« pÃ«rpunonit programet 
qÃ« po pÃ«rdornit dhe tÃ« vazhdonit tÃ« pÃ«rpunonit me ta. Pra, kishim njÃ« 
sistem qÃ« qe i dobishÃ«m pÃ«r gjÃ«ra tÃ« tjera veÃ§ programimit, dhe 
ndÃ«rkohÃ« mund ta programonit kur nga ana tjetÃ«r e pÃ«rdornit. Nuk e di nÃ«se 
qe e para ndÃ«r gjÃ«ra tÃ« tilla, por sigurisht qe pÃ«rpunuesi i parÃ« i 
tillÃ«."
+
+# type: Content of: <p>
+msgid "This spirit of building up gigantic, complicated programs to use in 
your own editing, and then exchanging them with other people, fueled the spirit 
of free-wheeling cooperation that we had at the AI Lab then. The idea was that 
you could give a copy of any program you had to someone who wanted a copy of 
it. We shared programs to whomever wanted to use them, they were human 
knowledge. So even though there was no organized political thought relating the 
way we shared software to the design of Emacs, I'm convinced that there was a 
connection between them, an unconscious connection perhaps. I think that it's 
the nature of the way we lived at the AI Lab that led to Emacs and made it what 
it was."
+msgstr "Kjo frymÃ« e krijimit tÃ« programeve gjigante, tÃ« ndÃ«rlikuara, pÃ«r 
pÃ«rdorim pÃ«r pÃ«rpunimin tuaj, e mandej shkÃ«mbimi i tyre me persona tÃ« 
tjerÃ«, ndezi frymÃ«n e bashkÃ«punimit tÃ« lirÃ« qÃ« shihnim atÃ«herÃ« nÃ« AI 
Lab. Ideja qÃ« mund t'ia jepnit kopjen e Ã§farÃ«do programi qÃ« kishit dikujt 
qÃ« donte njÃ« kopje tÃ« tij. I ndanim programet me kÃ«do qÃ« donte t'i 
pÃ«rdorte ato, pÃ«rbÃ«nin dije njerÃ«zore. Pra edhe pse nuk kish mendim politik 
tÃ« kristalizuar qÃ« tÃ« lidhej me mÃ«nyrÃ«n sipas tÃ« cilÃ«s shkÃ«mbenim 
<em>software</em> pÃ«r hartimin e Emacs-it, jam i bindur qÃ« pat njÃ« lidhje 
mes tyre, ndoshta njÃ« lidhje jo tÃ« vetÃ«dijshme. Mendoj se Ã«shtÃ« natyra e 
mÃ«nyrÃ«s se si jetonim nÃ« AI Lab ajo qÃ« shpuri te Emacs dhe e bÃ«ri atÃ« qÃ« 
Ã«shtÃ«."
+
+# type: Content of: <p>
+msgid "The original Emacs did not have Lisp in it. The lower level language, 
the non-interpreted language &mdash; was <abbr>PDP</abbr>-10 Assembler. The 
interpreter we wrote in that actually wasn't written for Emacs, it was written 
for <acronym title=\"Text Editor and COrrector\">TECO</acronym>. It was our 
text editor, and was an extremely ugly programming language, as ugly as could 
possibly be. The reason was that it wasn't designed to be a programming 
language, it was designed to be an editor and command language. There were 
commands like &lsquo;5l&rsquo;, meaning &lsquo;move five lines&rsquo;, or 
&lsquo;i&rsquo; and then a string and then an ESC to insert that string. You 
would type a string that was a series of commands, which was called a command 
string. You would end it with ESC ESC, and it would get executed."
+msgstr "Emacs-i origjinal nuk pÃ«rmbante Lisp. Gjuha e nivelit tÃ« ulÃ«t, 
gjuha e painterpretueshme &mdash; qe <abbr>PDP</abbr>-10 Assembler. 
Interpretuesi qÃ« shkruajtÃ«m nÃ« fakt nuk u shkruajt pÃ«r Emacs, u shkruajt 
pÃ«r <acronym title=\"Text Editor and COrrector\">TECO</acronym>. Ky qe 
pÃ«rpunuesi ynÃ« i teksteve, dhe qe njÃ« gjuhÃ« programimi tejet e shpifur, e 
shpifur sa mÃ« s'bÃ«hej. Arsyeja qe se nuk qe hartuar pÃ«r tÃ« qenÃ« gjuhÃ« 
programimi, qe hartuar pÃ«r tÃ« qenÃ« gjuhÃ« pÃ«rpunuesi dhe urdhrash. Kish 
urdhra tÃ« tilla si &lsquo;5l&rsquo;, pÃ«r &lsquo;zhvendosu pesÃ« 
rreshta&rsquo;, ose &lsquo;i&rsquo; e mandej njÃ« varg e mandej njÃ« ESC pÃ«r 
ta futur atÃ« varg diku. Mund tÃ« shkruanit njÃ« varg qÃ« mund tÃ« ishte njÃ« 
radhÃ« urdhrash, e qÃ« quhej varg urdhrash. E pÃ«rfundonit me ESC ESC, dhe 
kÃ«shtu mund tÃ« ekzekutohej."
+
+# type: Content of: <p>
+msgid "Well, people wanted to extend this language with programming 
facilities, so they added some. For instance, one of the first was a looping 
construct, which was &lt; &gt;. You would put those around things and it would 
loop. There were other cryptic commands that could be used to conditionally 
exit the loop.  To make Emacs, we <a href=\"#foot-7\">(7)</a> added facilities 
to have subroutines with names. Before that, it was sort of like Basic, and the 
subroutines could only have single letters as their names. That was hard to 
program big programs with, so we added code so they could have longer names. 
Actually, there were some rather sophisticated facilities; I think that Lisp 
got its unwind-protect facility from <acronym>TECO</acronym>."
+msgstr "NjerÃ«zit donin ta zgjeronin kÃ«tÃ« gjuhÃ« me aftÃ«si programimi, ndaj 
edhe shtuan ca syresh. PÃ«r shembull, nga tÃ« parat qe njÃ« mekanizÃ«m 
pÃ«rsÃ«ritjeje, qÃ« qe &lt; &gt;. Mund t'i vinit kÃ«to rreth njÃ« gjÃ«je dhe 
kjo gjÃ« do tÃ« pÃ«rsÃ«ritej. Kish edhe tÃ« tjera urdhra tÃ« mistershme qÃ« 
mund tÃ« pÃ«rdoreshin pÃ«r tÃ« dalÃ« nga pÃ«rsÃ«ritja sipas njÃ« kushti.  PÃ«r 
tÃ« krijuar Emacs-in, na <a href=\"#foot-7\">(7)</a> u desh tÃ« shtonim 
aftÃ«sinÃ« pÃ«r tÃ« pasur nÃ«nrutina tÃ« emÃ«rtuara. Para kÃ«saj, qe pak a 
shumÃ« si Basic, dhe nÃ«nrutinat mund tÃ« kishin vetÃ«m njÃ« shkronjÃ« si 
emÃ«r. Me to qe e vÃ«shtirÃ« tÃ« programoheshin programe tÃ« mÃ«dhaja, ndaj 
shtuam kod qÃ« tÃ« mund tÃ« kiheshin emra tÃ« gjatÃ«. NÃ« fakt, kish edhe disa 
aftÃ«si tÃ« tjera tÃ« sofistikuara; kam pÃ«rshtypjen se Lisp-i, aftÃ«sinÃ« pÃ«r 
\"unwind-protect\", e mori nga <acronym>TECO</acronym>."
+
+# type: Content of: <p>
+msgid "We started putting in rather sophisticated facilities, all with the 
ugliest syntax you could ever think of, and it worked &mdash; people were able 
to write large programs in it anyway. The obvious lesson was that a language 
like <acronym>TECO</acronym>, which wasn't designed to be a programming 
language, was the wrong way to go. The language that you build your extensions 
on shouldn't be thought of as a programming language in afterthought; it should 
be designed as a programming language. In fact, we discovered that the best 
programming language for that purpose was Lisp."
+msgstr "Filluam duke shtuar aftÃ«si pak a shumÃ« tÃ« sofistikuara, krejt me 
sintaksÃ«n mÃ« tÃ« shpifur qÃ« mund tÃ« mendoni, dhe funksionoi &mdash; 
njerÃ«zit qenÃ« tÃ« zotÃ«t tÃ« shkruanin programe tÃ« mÃ«dhenj me tÃ« 
prapÃ«seprapÃ«. MÃ«simi i qartÃ« qe qÃ« njÃ« gjuhÃ« si <acronym>TECO</acronym>, 
e cila nuk qe hartuar pÃ«r tÃ« qenÃ« gjuhÃ« programimi, ishte rruga e gabuar. 
GJuha nÃ« tÃ« cilÃ«n ju do tÃ« krijonit zgjerimet tuaja nuk do tÃ« duhej 
konceptuar si gjuhÃ« programimi pas tÃ« vjelÃ«s; do duhej konceptuar si gjuhÃ« 
programimi. NÃ« fakt, zbuluam qÃ« gjuha mÃ« e mirÃ« e programimit pÃ«r kÃ«tÃ« 
qÃ«llim qe Lisp-i."
+
+# type: Content of: <p>
+msgid "It was Bernie Greenberg, who discovered that it was <a 
href=\"#foot-5\">(5)</a>.  He wrote a version of Emacs in Multics MacLisp, and 
he wrote his commands in MacLisp in a straightforward fashion. The editor 
itself was written entirely in Lisp. Multics Emacs proved to be a great success 
&mdash; programming new editing commands was so convenient that even the 
secretaries in his office started learning how to use it. They used a manual 
someone had written which showed how to extend Emacs, but didn't say it was a 
programming. So the secretaries, who believed they couldn't do programming, 
weren't scared off. They read the manual, discovered they could do useful 
things and they learned to program."
+msgstr "Ai qÃ« e zbuloi kÃ«tÃ« <a href=\"#foot-5\">(5)</a>, qe Bernie 
Greenberg.  Ai shkroi njÃ« version tÃ« Emacs-it nÃ« Multics MacLisp, dhe i 
shkroi urdhrat e veta nÃ« MacLisp nÃ« mÃ«nyrÃ« tÃ« drejtpÃ«rdrejtÃ«. 
PÃ«rpunuesi nÃ« vetvete qe shkruajtur krejtÃ«sisht nÃ« Lisp. Multics Emacs u 
shndÃ«rrua nÃ« sukses tÃ« madh &mdash; programimi i urdhrave tÃ« rinj pÃ«r 
pÃ«rpunimin qe kaq i pÃ«rshtatshÃ«m sa edhe sekretaret nÃ« zyrÃ«n e tij filluan 
tÃ« mÃ«sonin se si ta pÃ«rdornin. PÃ«rdorÃ«n njÃ« doracak qÃ« e pat shkrojtur 
dikush e qÃ« tregonte se si tÃ« zgjerohej Emacs-i, por qÃ« nuk thoshte se 
bÃ«hej fjalÃ« pÃ«r programim. KÃ«shtu qÃ« sekretaret, qÃ« besonin se nuk 
programonin dot, nuk qenÃ« trembur. Lexuan doracakun, zbuluan qÃ« mund tÃ« 
bÃ«nin gjÃ«ra tÃ« dobishme dhe mÃ«suan tÃ« programonin."
+
+# type: Content of: <p>
+msgid "So Bernie saw that an application &mdash; a program that does something 
useful for you &mdash; which has Lisp inside it and which you could extend by 
rewriting the Lisp programs, is actually a very good way for people to learn 
programming. It gives them a chance to write small programs that are useful for 
them, which in most arenas you can't possibly do. They can get encouragement 
for their own practical use &mdash; at the stage where it's the hardest &mdash; 
where they don't believe they can program, until they get to the point where 
they are programmers."
+msgstr "Pra Bernie pa qÃ« njÃ« zbatim &mdash; njÃ« program qÃ« bÃ«n diÃ§ka tÃ« 
dobishme pÃ«r ju &mdash; qÃ« ka brenda Lisp dhe qÃ« mund ta zgjeroni duke 
rishkruajtur programe Lisp, Ã«shtÃ« nÃ« fakt njÃ« mÃ«nyrÃ« shumÃ« e mirÃ« qÃ« 
njerÃ«zit tÃ« mÃ«sojnÃ« programim. U jep atyre njÃ« mundÃ«si tÃ« shkruajnÃ« 
programe tÃ« vegjÃ«l qÃ« janÃ« tÃ« dobishÃ«m pÃ«r ta, Ã§ka nÃ« shumicÃ«n e 
fushave ju ndoshta nuk mund ta kryeni dot. Mund tÃ« nxiten pÃ«rmes pÃ«rdorimit 
praktik &mdash; nÃ« fazÃ«n qÃ« Ã«shtÃ« mÃ« e vÃ«shtira &mdash; kur nuk besojnÃ« 
se mund tÃ« programojnÃ«, deria arrijnÃ« nÃ« pikÃ«n qÃ« janÃ« programuesa."
+
+# type: Content of: <p>
+msgid "At that point, people began to wonder how they could get something like 
this on a platform where they didn't have full service Lisp implementation. 
Multics MacLisp had a compiler as well as an interpreter &mdash; it was a 
full-fledged Lisp system &mdash; but people wanted to implement something like 
that on other systems where they had not already written a Lisp compiler. Well, 
if you didn't have the Lisp compiler you couldn't write the whole editor in 
Lisp &mdash; it would be too slow, especially redisplay, if it had to run 
interpreted Lisp.  So we developed a hybrid technique. The idea was to write a 
Lisp interpreter and the lower level parts of the editor together, so that 
parts of the editor were built-in Lisp facilities. Those would be whatever 
parts we felt we had to optimize. This was a technique that we had already 
consciously practiced in the original Emacs, because there were certain fairly 
high level features which we re-implemented in machine language, making them 
into <acronym>TECO</acronym> primitives. For instance, there was a 
<acronym>TECO</acronym> primitive to fill a paragraph (actually, to do most of 
the work of filling a paragraph, because some of the less time-consuming parts 
of the job would be done at the higher level by a <acronym>TECO</acronym> 
program). You could do the whole job by writing a <acronym>TECO</acronym> 
program, but that was too slow, so we optimized it by putting part of it in 
machine language. We used the same idea here (in the hybrid technique), that 
most of the editor would be written in Lisp, but certain parts of it that had 
to run particularly fast would be written at a lower level."
+msgstr "NÃ« kÃ«tÃ« pikÃ«, njerÃ«zit zunÃ« tÃ« mendonin se si mund tÃ« kishin 
diÃ§ka tÃ« tillÃ« edhe nÃ« njÃ« platformÃ« tek e cila nuk kishin sendÃ«rtim tÃ« 
plotÃ« funksional tÃ« Lisp-it. Multics MacLisp kish njÃ« pÃ«rpilues dhe njÃ« 
interpretues &mdash; qe sistem Lisp i kompletuar &mdash; por njerÃ«zit donin 
tÃ« sendÃ«rtonin diÃ§ka tÃ« tillÃ« nÃ« sisteme tÃ« tjera ku nuk kishin 
shkruajtur akoma ndonjÃ« pÃ«rpilues Lisp. Pra, po tÃ« mos kishit pÃ«rpiluesin 
Lisp, nuk shkruanit dot plotÃ«sisht pÃ«rpunuesin nÃ« Lisp &mdash; do tÃ« ishte 
shumÃ« i ngadaltÃ«, veÃ§anÃ«risht riparaqitja, po qe se bÃ«hej fjalÃ« tÃ« 
xhirohej Lisp i interpretuar.  Ndaj zhvilluam njÃ« teknikÃ« hibride. Ideja qe 
tÃ« shkruanim nÃ« njÃ« tÃ« vetÃ«m njÃ« interpretues Lisp dhe pjesÃ«t e nivelit 
tÃ« ulÃ«t tok, qÃ« kÃ«shtu njÃ« pjesÃ« e pÃ«rpunuesit tÃ« qenÃ« pjesÃ« tÃ« 
brendshme tÃ« Lisp-it. KÃ«to do tÃ« ishin Ã§farÃ«do pjesÃ«sh qÃ« ne mendonim se 
duheshin pÃ«rsosur. Kjo qe njÃ« teknikÃ« qÃ« e kishim praktikuar tashmÃ« me 
vetÃ«dije nÃ« Emacs-in origjinal, ngaqÃ« kish disa veÃ§ori deri diku tÃ« 
nivelit tÃ« lartÃ«, tÃ« cilat i risendÃ«rtuam nÃ« gjuhÃ«n e makinÃ«s, duke i 
shndÃ«rruar nÃ« primitivÃ« <acronym>TECO</acronym>. pÃ«r shembull, kish njÃ« 
primitiv <acronym>TECO</acronym> pÃ«r mbushjen e njÃ« paragrafi (nÃ« fakt, pÃ«r 
kryerjen e shumicÃ«s sÃ« punÃ«s pÃ«r mbushjen e njÃ« paragrafi, ngaqÃ« disa nga 
pjesÃ«t mÃ« pak tÃ« lodhshme tÃ« punÃ«s i binte tÃ« kryheshin nÃ« njÃ« nivel 
mÃ« tÃ« lartÃ«, nga njÃ« program <acronym>TECO</acronym>). Mund ta bÃ«nit krejt 
punÃ«n duke shkruajtur njÃ« program <acronym>TECO</acronym>, por kjo qe shumÃ« 
e ngadaltÃ«, ndaj e pÃ«rsosÃ«m duke hedhur pjesÃ« tÃ« tij nÃ« gjuhÃ«n e 
makinÃ«s. PÃ«rdorÃ«m kÃ«tu tÃ« njÃ«jtÃ«n ide (atÃ« te teknika hibride), qÃ« 
pjesa dÃ«rrmuese e pÃ«rpunuesit tÃ« shkruhej nÃ« Lisp, por disa pjesÃ« tÃ« tij, 
tÃ« cilat duhej tÃ« xhironin veÃ§anÃ«risht shpejt, tÃ« shkruheshin nÃ« nivel 
mÃ« tÃ« ulÃ«t."
+
+# type: Content of: <p>
+msgid "Therefore, when I wrote my second implementation of Emacs, I followed 
the same kind of design. The low level language was not machine language 
anymore, it was C. C was a good, efficient language for portable programs to 
run in a Unix-like operating system. There was a Lisp interpreter, but I 
implemented facilities for special purpose editing jobs directly in C &mdash; 
manipulating editor buffers, inserting leading text, reading and writing files, 
redisplaying the buffer on the screen, managing editor windows."
+msgstr "KÃ«shtu qÃ«, kur shkrojta sendÃ«rtimin tim tÃ« dytÃ« tÃ« Emacs-it, 
ndoqa tÃ« njÃ«jtÃ«n lloj skeme. Gjuha e nivelit tÃ« ulÃ«t nuk qe mÃ« gjuha e 
makinÃ«s, qe C-ja. C-ja qe gjuhÃ« e mirÃ«, e efektshme pÃ«r programe tÃ« 
kalueshÃ«m, qÃ« tÃ« mund tÃ« xhironin nÃ« njÃ« sistem operativ tÃ« ngjashÃ«m me 
Unix-in. Kishte njÃ« interpretues Lisp, por sendÃ«rtova aftÃ«si pÃ«r veprime 
specifike pÃ«rpunimi drejt e nÃ« C &mdash; pÃ«rdorim shtytÃ«zash pÃ«rpunuesi, 
futjeje teksi drejtues, lexim dhe shkrim kartelash, rishfaqje nÃ« ekran e 
pÃ«rmbajtjes sÃ« njÃ« shtytÃ«ze, administrim dritaresh pÃ«rpunuesi."
+
+# type: Content of: <p>
+msgid "Now, this was not the first Emacs that was written in C and ran on 
Unix. The first was written by James Gosling, and was referred to as GosMacs. A 
strange thing happened with him. In the beginning, he seemed to be influenced 
by the same spirit of sharing and cooperation of the original Emacs. I first 
released the original Emacs to people at <abbr>MIT</abbr>. Someone wanted to 
port it to run on Twenex &mdash; it originally only ran on the Incompatible 
Timesharing System we used at <abbr>MIT</abbr>. They ported it to Twenex, which 
meant that there were a few hundred installations around the world that could 
potentially use it. We started distributing it to them, with the rule that 
&ldquo;you had to send back all of your improvements&rdquo; so we could all 
benefit. No one ever tried to enforce that, but as far as I know people did 
cooperate."
+msgstr "Tani, ky nuk qe Emacs-i i parÃ« i shkruajtur nÃ« C dhe qÃ« xhironte 
nÃ«n Unix. I pari qe shkruajtur nga James Gosling, dhe i referoheshin si 
GosMacs. I ndodhi diÃ§ka e Ã§uditshme. NÃ« fillim, ngjante se ndikohej nga e 
njÃ«jta frymÃ« e shkÃ«mbimit dhe bashkÃ«punimit me Emacs-in origjinal. Emacs-in 
e parÃ« origjinal e pata hedhur nÃ« qarkullim pÃ«r personat nÃ« 
<abbr>MIT</abbr>. Dikush dÃ«shironte ta bÃ«nte tÃ« xhironte nÃ«  Twenex &mdash; 
nÃ« fillim xhironte vetÃ«m nÃ« <i>Incompatible Timesharing System</i> qÃ« 
pÃ«rdornim nÃ« <abbr>MIT</abbr>. E kaluan nÃ« Twenex, qÃ« do tÃ« thoshte se 
kish ndoca qindra instalime nÃ«pÃ«r botÃ« qÃ« mundej ta pÃ«rdornin. ZumÃ« tua 
dÃ«rgonim atyre, me kusht qÃ« &ldquo;duhet tÃ« na dÃ«rgoni krejt pÃ«rmirÃ«simet 
qÃ« i bÃ«ni&rdquo; qÃ« tÃ« pÃ«rfitonim tÃ« gjithÃ«. Askush nuk u pÃ«rpoq ta 
bÃ«nte kÃ«tÃ« tÃ« detyrueshme, por me aq sa di pati bashkÃ«punim."
+
+# type: Content of: <p>
+msgid "Gosling did, at first, seem to participate in this spirit. He wrote in 
a manual that he called the program Emacs hoping that others in the community 
would improve it until it was worthy of that name. That's the right approach to 
take towards a community &mdash; to ask them to join in and make the program 
better. But after that he seemed to change the spirit, and sold it to a 
company."
+msgstr "Gosling dukej, nÃ« fillim, se do tÃ« bashkÃ«punonte nÃ« kÃ«tÃ« frymÃ«. 
Shkrojti nÃ« njÃ« njÃ« doracak se po e quante program Emacs duke shpresuar qÃ« 
edhe tÃ« tjerÃ« nga bashkÃ«sia do ta pÃ«rmirÃ«sonin derisa t'ia vlente atÃ« 
emÃ«r. Ky qe trajtimi i duhur karshi njÃ« bashkÃ«sie &mdash; t'u kÃ«rkohej tÃ« 
merrnin pjesÃ« e ta bÃ«nin programin mÃ« tÃ« mirÃ«. Por pas kÃ«saj dukej se 
ndÃ«rroi mendje, dhe ia shiti njÃ« shoqÃ«rie."
+
+# type: Content of: <p>
+msgid "At that time I was working on the GNU system (a free software Unix-like 
operating system that many people erroneously call &ldquo;Linux&rdquo;).  There 
was no free software Emacs editor that ran on Unix. I did, however, have a 
friend who had participated in developing Gosling's Emacs. Gosling had given 
him, by email, permission to distribute his own version. He proposed to me that 
I use that version. Then I discovered that Gosling's Emacs did not have a real 
Lisp. It had a programming language that was known as &lsquo;mocklisp&rsquo;, 
which looks syntactically like Lisp, but didn't have the data structures of 
Lisp.  So programs were not data, and vital elements of Lisp were missing.  Its 
data structures were strings, numbers and a few other specialized things."
+msgstr "NÃ« kohÃ«n qÃ« po punoja pÃ«r sistemin GNU (njÃ« sistem operativ 
<em>software</em> i lirÃ«, i ngjashÃ«m me Unix qÃ« mjaft vetÃ« gabimisht e 
quajnÃ« &ldquo;Linux&rdquo;).  Nuk kish pÃ«rpunues Emacs, si <em>software</em> 
tÃ« lirÃ«, qÃ« xhironte nÃ«n Unix. Kisha, megjithÃ«kÃ«tÃ«, njÃ« shok qÃ« kish 
marrÃ« pjesÃ« nÃ« programimin e Emacs-it tÃ« Gosling-ut. Gosling-u i pat 
dhÃ«nÃ«, pÃ«rmes email-i, leje tÃ« pÃ«rhapte versione tÃ« tijat. MÃ« propozoi 
tÃ« pÃ«rdorja atÃ« version. MÃ« tej pashÃ« qÃ« Emacs-i Gosling-ut nuk 
pÃ«rmbante Lisp tÃ« vÃ«rtetÃ«. Kish njÃ« gjuhÃ« programimi qÃ« njihej si 
&lsquo;mocklisp&rsquo;, qÃ« nga sintaksa duket si Lisp, por qÃ« nuk kish 
struktura tÃ« dhÃ«nash tÃ« Lisp-it.  KÃ«shtu qÃ« programet nuk qenÃ« tÃ« 
dhÃ«na, dhe mungonin elemente jetike tÃ« Lisp-it.  Strukturat e tÃ« dhÃ«nave 
nÃ« tÃ« qenÃ« vargje, numra dhe pak gjÃ«ra tÃ« tjera speciale."
+
+# type: Content of: <p>
+msgid "I concluded I couldn't use it and had to replace it all, the first step 
of which was to write an actual Lisp interpreter. I gradually adapted every 
part of the editor based on real Lisp data structures, rather than ad hoc data 
structures, making the data structures of the internals of the editor exposable 
and manipulable by the user's Lisp programs."
+msgstr "Dola nÃ« pÃ«rfundimin se nuk e pÃ«rdorja dot dhe mÃ« duhej ta 
zÃ«vendÃ«soja tÃ« tÃ«rin, hapi i parÃ« pÃ«r tÃ« cilin qe shkrimi i njÃ« 
interpretuesi tÃ« vÃ«rtetÃ« Lisp. Dora-dorÃ«s pÃ«rshtata Ã§do pjesÃ« tÃ« 
pÃ«rpunuesit duke e bazuar nÃ« struktura tÃ« dhÃ«nash Lisp faktike, nÃ« vend 
tÃ« strukturave <i>ad hoc</i> pÃ«r tÃ« dhÃ«nat, duke i bÃ«rÃ« strukturat e tÃ« 
dhÃ«nave tÃ« mekanizmave tÃ« brendshme tÃ« pÃ«rpunuesit tÃ« ekspozueshme dhe 
tÃ« trajtueshme nga programet Lisp tÃ« pÃ«rdoruesit."
+
+# type: Content of: <p>
+msgid "The one exception was redisplay. For a long time, redisplay was sort of 
an alternate world. The editor would enter the world of redisplay and things 
would go on with very special data structures that were not safe for garbage 
collection, not safe for interruption, and you couldn't run any Lisp programs 
during that. We've changed that since &mdash; it's now possible to run Lisp 
code during redisplay. It's a quite a convenient thing."
+msgstr "PÃ«rjashtim qe rishfaqja. PÃ«r shumÃ« kohÃ«, rishfaqja qe njÃ«farÃ« 
bote tjetÃ«r. PÃ«rpunuesi mund tÃ« kalonte nÃ« botÃ«n e rishfaqjeve dhe gjÃ«rat 
do tÃ« vazhdonin me struktura tÃ« dhÃ«nash tejet speciale qÃ« nuk qenÃ« pa dÃ«m 
pÃ«r grumbullim hedhurinash, as pÃ«r ndÃ«rprerje, dhe nuk mund tÃ« xhironi 
ndonjÃ« program Lisp gjatÃ« kohÃ«s qÃ« ndodhte kjo. E ndryshuam ama &mdash; 
tani Ã«shtÃ« e mundur tÃ« xhirohet kod Lisp gjatÃ« rishfaqjes. GjÃ« pa zarar."
+
+# type: Content of: <p>
+msgid "This second Emacs program was &lsquo;free software&rsquo; in the modern 
sense of the term &mdash; it was part of an explicit political campaign to make 
software free. The essence of this campaign was that everybody should be free 
to do the things we did in the old days at <abbr>MIT</abbr>, working together 
on software and working with whomever wanted to work with us.  That is the 
basis for the free software movement &mdash; the experience I had, the life 
that I've lived at the <abbr>MIT</abbr> AI lab &mdash; to be working on human 
knowledge, and not be standing in the way of anybody's further using and 
further disseminating human knowledge."
+msgstr "Ky program i dytÃ« Emacs qe &lsquo;<em>software</em> i lirÃ«&rsquo; 
nÃ« kuptimin modern tÃ« fjalÃ«s &mdash; qe pjesÃ« e njÃ« fushate tÃ« deklaruar 
politike pÃ«r krijim <em>software</em>-i tÃ« lirÃ«. Thelbi i kÃ«saj fushate qe 
qÃ« kushdo duhet tÃ« jetÃ« i lirÃ« tÃ« bÃ«jÃ« gjÃ«rat qÃ« bÃ«nim ne dikur nÃ« 
<abbr>MIT</abbr>, tÃ« punohej tok mbi <em>software</em>-e dhe tÃ« punohej me 
kÃ«do qÃ« donte tÃ« punonte me ne.  Kjo Ã«shtÃ« baza e lÃ«vizjes pÃ«r 
<em>software</em> tÃ« lirÃ« &mdash; pÃ«rvoja qÃ« pata, jeta qÃ« bÃ«ja nÃ« 
<abbr>MIT</abbr> AI lab &mdash; tÃ« punohej pÃ«r dijen njerÃ«zore, dhe jo t'i 
zihej rruga cilitdo qÃ« pÃ«rdorte dhe pÃ«rhapte mÃ« tej dijen njerÃ«zore."
+
+# type: Content of: <p>
+msgid "At the time, you could make a computer that was about the same price 
range as other computers that weren't meant for Lisp, except that it would run 
Lisp much faster than they would, and with full type checking in every 
operation as well. Ordinary computers typically forced you to choose between 
execution speed and good typechecking.  So yes, you could have a Lisp compiler 
and run your programs fast, but when they tried to take <tt>car</tt> of a 
number, it got nonsensical results and eventually crashed at some point."
+msgstr "NÃ« atÃ« kohÃ«, mund tÃ« bÃ«nit njÃ« kompjuter qÃ« hynte nÃ« po atÃ« 
segment Ã§mimesh si kompjuterat e tjerÃ« qÃ« nuk qenÃ« menduar pÃ«r Lisp, 
vetÃ«m se ky mund tÃ« xhironte Lisp-in shumÃ« mÃ« shpejt se ata, dhe me 
kontroll tÃ« plotÃ« tÃ« llojit tÃ« tÃ« dhÃ«nave nÃ« Ã§do veprim, po ashtu. 
Kompjuterat ezakonshÃ«m ju shtrÃ«ngonin tÃ« zgjidhnit o shpejtÃ«sinÃ« e 
ekzekutimit, o kontroll tÃ« mirÃ« tÃ« llojit tÃ« tÃ« dhÃ«nave.  Pra, mund tÃ« 
kihej njÃ« pÃ«rpilues Lisp dhe tÃ« xhiroheshin programet mÃ« shpejt, por kur 
provohej tÃ« merrej <tt>automjeti</tt> i njÃ« targe, arrihej nÃ« pÃ«rfundime pa 
kuptim dhe nÃ« vazhdim deri nÃ« vithisje."
+
+# type: Content of: <p>
+msgid "The Lisp machine was able to execute instructions about as fast as 
those other machines, but each instruction &mdash; a car instruction would do 
data typechecking &mdash; so when you tried to get the car of a number in a 
compiled program, it would give you an immediate error. We built the machine 
and had a Lisp operating system for it. It was written almost entirely in Lisp, 
the only exceptions being parts written in the microcode. People became 
interested in manufacturing them, which meant they should start a company."
+msgstr "Makina Lisp qe e zonja tÃ« pÃ«rmbushte udhÃ«zimet gati po aq shpejt sa 
makinat e tjera, por Ã§do udhÃ«zim &mdash; udhÃ«zimi \"automjet\" do tÃ« 
shkaktonte kontroll lloji tÃ« dhÃ«nash &mdash; kÃ«shtu qÃ« po tÃ« provonit tÃ« 
kÃ«rkonit automjetin e njÃ« numri, nÃ« njÃ« program tÃ« pÃ«rpiluar, do t'ju 
paraqitej menjÃ«herÃ« njÃ« gabim. E ndÃ«rtuan makinÃ«n dhe kjo pati njÃ« sistem 
operativ Lisp. Qe shkruajtur kjretÃ«sisht nÃ« Lisp, me pÃ«rjashtim vetÃ«m tÃ« 
pjesÃ«ve tÃ« shkruajtura nÃ« mikrokod. NjerÃ«zve filloi t'u interesojÃ« 
prodhimi i tyre, qÃ« do tÃ« thoshte se mund tÃ« fillonin njÃ« biznes."
+
+# type: Content of: <p>
+msgid "There were two different ideas about what this company should be like.  
Greenblatt wanted to start what he called a &ldquo;hacker&rdquo; company. This 
meant it would be a company run by hackers and would operate in a way conducive 
to hackers. Another goal was to maintain the AI Lab culture <a 
href=\"#foot-1\">(1)</a>.  Unfortunately, Greenblatt didn't have any business 
experience, so other people in the Lisp machine group said they doubted whether 
he could succeed. They thought that his plan to avoid outside investment 
wouldn't work."
+msgstr "Kish dy ide tÃ« ndryshme rreth se si mund tÃ« ishte shoqÃ«ria.  
Greenblatt-i donte tÃ« fillonte atÃ« Ã§ka e quante shoqÃ«ri 
&ldquo;hacker-ash&rdquo;. Kjo donte tÃ« thoshte njÃ« shoqÃ«ri e administruar 
nga <i>hackers</i> dhe do tÃ« funksiononte nÃ« njÃ« mÃ«nyrÃ« nxitÃ«se pÃ«r 
<i>hackers</i>-at. NjÃ« synim tjetÃ«r qÃ« tÃ« vazhdohej kultura e laobratorit 
AI Lab <a href=\"#foot-1\">(1)</a>.  PÃ«r fat tÃ« keq, Greenblatt-i nuk kish 
ndonjÃ« pÃ«rvojÃ« nÃ« punÃ« biznesi, ndaj tÃ« tjerÃ« persona nÃ« grupin e 
makinave Lisp thanÃ« se dyshonin se mund t'ia dilte mbanÃ«. QenÃ« tÃ« mendimit 
qÃ« plani i tij pÃ«r tÃ« shmangur investime nga jashtÃ« grupit nuk kish pÃ«r 
tÃ« funksionuar."
+
+# type: Content of: <p>
+msgid "Why did he want to avoid outside investment? Because when a company has 
outside investors, they take control and they don't let you have any scruples. 
And eventually, if you have any scruples, they also replace you as the manager."
+msgstr "Pse donte tÃ« shmangte investimet nga jashtÃ«? NgaqÃ« kur njÃ« 
shoqÃ«ri ka investitorÃ« jashtÃ« vetes, kÃ«ta shtien nÃ« dorÃ« kontrollin dhe 
nuk ju lÃ«nÃ« mÃ« tÃ« keni skrupuj. Dhe nÃ« fund, po patÃ«t skrupuj, ju heqin 
nga drejtimi."
+
+# type: Content of: <p>
+msgid "So Greenblatt had the idea that he would find a customer who would pay 
in advance to buy the parts. They would build machines and deliver them; with 
profits from those parts, they would then be able to buy parts for a few more 
machines, sell those and then buy parts for a larger number of machines, and so 
on. The other people in the group thought that this couldn't possibly work."
+msgstr "Ndaj Greenblatt-i pati idenÃ« tÃ« gjente klientÃ« qÃ« do tÃ« 
parapaguanin blerjen e pjesÃ«ve. TÃ« montonin makinat dhe t'i shpÃ«rndanin te 
porositÃ«sit; me fitimin prej pjesÃ«ve, do tÃ« ishin nÃ« gjendje tÃ« blenin 
pjesÃ« pÃ«r ndoca makina tÃ« tjera, t'i shisnin kÃ«to e mandej tÃ« blinin 
pjesÃ« pÃ«r njÃ« numÃ«r mÃ« tÃ« madh makinash, e me radhÃ«. Personat e tjerÃ« 
nÃ« grup qenÃ« tÃ« mendimit qÃ« kjo do tÃ« funksiononte."
+
+# type: Content of: <p>
+msgid "Greenblatt then recruited Russell Noftsker, the man who had hired me, 
who had subsequently left the AI Lab and created a successful company.  Russell 
was believed to have an aptitude for business. He demonstrated this aptitude 
for business by saying to the other people in the group, &ldquo;Let's ditch 
Greenblatt, forget his ideas, and we'll make another company.&rdquo; Stabbing 
in the back, clearly a real businessman. Those people decided they would form a 
company called Symbolics. They would get outside investment, not have scruples, 
and do everything possible to win."
+msgstr "KÃ«shtu Greenblatt-i mori nÃ« punÃ« Russell Noftsker-in, njeriun qÃ« 
mÃ« pat punÃ«suar mua, qÃ« mÃ« pas e pat lÃ«nÃ« laboratorin AI Lab dhe kish 
krijuar njÃ« shoqÃ«ri tÃ« suksesshme.  Russell-i besohej se kish nuhatje pÃ«r 
biznes. E shfaqi kÃ«tÃ« nuhatje pÃ«r biznes duke u thÃ«nÃ« personave tÃ« tjerÃ« 
tÃ« grupit, &ldquo;Le ta heqim qafe Greenblatt-in, bashkÃ« me idetÃ« e tij, dhe 
do tÃ« ngremÃ« njÃ« tjetÃ«r shoqÃ«ri.&rdquo; ThikÃ« pas shpine, biznesmen i 
vÃ«rtet sa mÃ« s'bÃ«het. KÃ«ta persona vendosÃ«n tÃ« krijonin njÃ« shoqÃ«ri tÃ« 
quajtur Symbolics. Me investime nga jashtÃ«, pa skrupuj, dhe  tÃ« gatshÃ«m pÃ«r 
gjithÃ§ka pÃ«r fitoren."
+
+# type: Content of: <p>
+msgid "But Greenblatt didn't give up. He and the few people loyal to him 
decided to start Lisp Machines Inc. anyway and go ahead with their plans. And 
what do you know, they succeeded! They got the first customer and were paid in 
advance. They built machines and sold them, and built more machines and more 
machines. They actually succeeded even though they didn't have the help of most 
of the people in the group. Symbolics also got off to a successful start, so 
you had two competing Lisp machine companies. When Symbolics saw that LMI was 
not going to fall flat on its face, they started looking for ways to destroy 
it."
+msgstr "Por Greenblatt-i nuk u dorÃ«zua. Ai dhe ata pak besnikÃ« tÃ« tij 
vendosÃ«n tÃ« krijonin Lisp Machines Inc. sido qÃ« tÃ« ndodhte dhe tÃ« ecnin 
para me planet e tyre. Dhe siÃ§ e dini, ia dolÃ«n mbanÃ«! GjetÃ«n klientin e 
parÃ« dhe patÃ«n parapagim. Montuan makina dhe i shitÃ«n, pastaj krijuan mÃ« 
shumÃ« makina, e prapÃ« tÃ« tjera. Ia dolÃ«n mbanÃ« edhe pse nuk patÃ«n 
ndihmÃ«n e shumicÃ«s sÃ« personave tÃ« grupit. Edhe Symbolics pati fillim tÃ« 
suksesshÃ«m, pra kishit dy shoqÃ«ri konkurruese makinash Lisp. Kur Symbolics pa 
qÃ« LMI nuk do tÃ« shkÃ«rrmoqej, filluan tÃ« kÃ«rkonin pÃ«r mÃ«nyra se si ta 
shkatÃ«rronin."
+
+# type: Content of: <p>
+msgid "Thus, the abandonment of our lab was followed by &ldquo;war&rdquo; in 
our lab.  The abandonment happened when Symbolics hired away all the hackers, 
except me and the few who worked at LMI part-time. Then they invoked a rule and 
eliminated people who worked part-time for <abbr>MIT</abbr>, so they had to 
leave entirely, which left only me. The AI lab was now helpless.  And 
<abbr>MIT</abbr> had made a very foolish arrangement with these two companies.  
It was a three-way contract where both companies licensed the use of Lisp 
machine system sources. These companies were required to let <abbr>MIT</abbr> 
use their changes. But it didn't say in the contract that <abbr>MIT</abbr> was 
entitled to put them into the <abbr>MIT</abbr> Lisp machine systems that both 
companies had licensed. Nobody had envisioned that the AI lab's hacker group 
would be wiped out, but it was."
+msgstr "KÃ«shtu qÃ« nÃ« laboratorin tonÃ« braktisja u pasua nga 
&ldquo;lufta&rdquo;.  Braktisja erdhi kur Symbolics punÃ«soi krejt 
<i>hacker</i>-at, hiq mua dhe ndoca qÃ« punonin me kohÃ« tÃ« pjesshme te LMI. 
Mandej nxorrÃ«n nga pluhuri njÃ« rregull dhe hoqn qafe personat qÃ« punonin me 
kohÃ« tÃ« pjesshme pÃ«r <abbr>MIT</abbr>-in, kÃ«shtu qÃ« iu desh tÃ« iknin 
plotÃ«sisht, e prej kÃ«saj mbeta vetÃ«m unÃ«. Laboratori AI tani qe i 
pashpresÃ«.  Dhe <abbr>MIT</abbr> kish bÃ«rÃ« njÃ« ujdi shumÃ« tÃ« marrÃ« me 
kÃ«to dy shoqÃ«ritÃ«.  Qe njÃ« kontratÃ« trikahÃ«she ku secila shoqÃ«ri lejonte 
pÃ«rdorimin e kodit burim tÃ« sistemit tÃ« makinave Lisp. KÃ«to shoqÃ«ri qenÃ« 
tÃ« detyruara tÃ« lejonin <abbr>MIT</abbr>-in tÃ« pÃ«rdorte ndryshime e bÃ«ra 
prej tyre. Po nuk thuhej nÃ« kontratÃ« qÃ« <abbr>MIT</abbr>-i gÃ«zonte tÃ« 
drejtÃ«n t'i hidhte ato nÃ« sistemet e makinave Lisp tÃ« <abbr>MIT</abbr>-it 
qÃ« qenÃ« lejuar nga tÃ« dyja shoqÃ«ritÃ«. Askush nuk pati Ã§uar nÃ« mendje qÃ« 
grupi i <i>hacker</i>-ave tÃ« laboratorit AI do tÃ« avullonte, por ja qÃ« 
ndodhi."
+
+# type: Content of: <p>
+msgid "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>.  They 
said to the lab, &ldquo;We will continue making our changes to the system 
available for you to use, but you can't put it into the <abbr>MIT</abbr> Lisp 
machine system. Instead, we'll give you access to Symbolics' Lisp machine 
system, and you can run it, but that's all you can do.&rdquo;"
+msgstr "KÃ«shtu qÃ« Symbolics hartoi njÃ« plan <a href=\"#foot-4\">(4)</a>.  I 
thanÃ« laboratorit, &ldquo;Do tÃ« vazhdojmÃ« t'ju lejojmÃ« pÃ«rdorimin e 
ndryshimeve tona, por nuk mund t'i hidhni sistemi <abbr>MIT</abbr> i makinave 
Lisp. NÃ« vend tÃ« kÃ«saj, do t'ju lejojmÃ« hyrje nÃ« sistemin e makinave Lisp 
tÃ« Symbolics-it, dhe mund ta xhironi, por kjo Ã«shtÃ« e gjitha Ã§ka mund tÃ« 
bÃ«ni.&rdquo;"
+
+# type: Content of: <p>
+msgid "This, in effect, meant that they demanded that we had to choose a side, 
and use either the <abbr>MIT</abbr> version of the system or the Symbolics 
version.  Whichever choice we made determined which system our improvements 
went to. If we worked on and improved the Symbolics version, we would be 
supporting Symbolics alone. If we used and improved the <abbr>MIT</abbr> 
version of the system, we would be doing work available to both companies, but 
Symbolics saw that we would be supporting LMI because we would be helping them 
continue to exist. So we were not allowed to be neutral anymore."
+msgstr "Kjo, praktikisht, do tÃ« thoshte qÃ« kÃ«rkuan tÃ« zgjidhmin me kÃ« 
palÃ« do tÃ« ishim, dhe tÃ« pÃ«rdornim ose versionin <abbr>MIT</abbr> tÃ« 
sistemit ose versionin Symbolics.  CilÃ«ndo zgjedhje tÃ« bÃ«nim, do tÃ« 
pÃ«rcaktonte se te cili sistem do tÃ« shkonin pÃ«rmirÃ«simet tona. Po tÃ« 
punonin me dhe tÃ« pÃ«rmirÃ«sonin versionin e Symbolics-it, do tÃ« mbÃ«shtesnim 
vetÃ«m Symbolics-in. Po tÃ« pÃ«rdornim dhe pÃ«rmirÃ«sonim versionin 
<abbr>MIT</abbr> tÃ« sistemit, i binte ta jepnim punÃ«n te tÃ« dyja 
shoqÃ«ritÃ«, por Symbolics pa qÃ« do ta mbÃ«shtesnim LMI ngaqÃ« do ta ndihmonim 
tÃ« ekzistonte. KÃ«shtu qÃ« nuk na u lejua tÃ« qÃ«ndronim ende asnjanÃ«s."
+
+# type: Content of: <p>
+msgid "Up until that point, I hadn't taken the side of either company, 
although it made me miserable to see what had happened to our community and the 
software.  But now, Symbolics had forced the issue.  So, in an effort to help 
keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> &mdash; I began 
duplicating all of the improvements Symbolics had made to the Lisp machine 
system.  I wrote the equivalent improvements again myself (i.e., the code was 
my own)."
+msgstr "Deri nÃ« atÃ« pikÃ«, nuk kisha mbajtur anÃ«n e asnjÃ«rÃ«s shoqÃ«ri, 
edhe pse ndihesha keq kur shihja se Ã§'i ndodhi bashkÃ«sisÃ« sonÃ« dhe 
<em>software</em>-it.  Por tashmÃ«, Symbolics-i e kish bÃ«rÃ« tÃ« detyruar 
kÃ«tÃ« gjÃ«.  E kÃ«shtu, nÃ« njÃ« pÃ«rpjekje pÃ«r ta mbajtur gjallÃ« Lisp 
Machines Inc. <a href=\"#foot-2\">(2)</a> &mdash; zura tÃ« riprodhoj krejt 
pÃ«rmirÃ«simet qÃ« Symbolics kish bÃ«rÃ« te sistemi i makinÃ«s Lisp.  I 
shkruajta vetÃ« pÃ«rmirÃ«simet e njÃ«vlefshme nga e para (dmth, kodi qe i imi)."
+
+# type: Content of: <p>
+msgid "After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion 
that it would be best if I didn't even look at their code. When they made a 
beta announcement that gave the release notes, I would see what the features 
were and then implement them. By the time they had a real release, I did too."
+msgstr "Pas ca kohÃ«sh <a href=\"#foot-3\">(3)</a>, mbÃ«rrita nÃ« pÃ«rfundimin 
qÃ« e mira e tÃ« mirave do tÃ« ishte tÃ« mos shihja fare nÃ« kodin e tyre. Kur 
njoftonin paraprakisht pÃ«r ndonjÃ« version beta, qÃ« shoqÃ«rohej me shÃ«nime 
versioni, mund tÃ« shihja Ã§'qenÃ« veÃ§oritÃ« e reja e mandej t'i sendÃ«rtoja. 
NÃ« kohÃ«n qÃ« hidhni faktikisht nÃ« qarkullim diÃ§ka, po atÃ« bÃ«ja edhe unÃ«."
+
+# type: Content of: <p>
+msgid "In this way, for two years, I prevented them from wiping out Lisp 
Machines Incorporated, and the two companies went on. But, I didn't want to 
spend years and years punishing someone, just thwarting an evil deed. I figured 
they had been punished pretty thoroughly because they were stuck with 
competition that was not leaving or going to disappear<a 
href=\"#foot-6\">(6)</a>. Meanwhile, it was time to start building a new 
community to replace the one that their actions and others had wiped out."
+msgstr "NÃ« kÃ«tÃ« mÃ«nyrÃ«, pÃ«r dy vite, ua pengova ta fshinin nga faqja e 
dheut Lisp Machines Incorporated, dhe tÃ« dy shoqÃ«ritÃ« bÃ«nÃ« pÃ«rpara. Por 
nuk doja tÃ« shpenzoja vite tÃ« tÃ«ra duke ndÃ«shkuar dikÃ«, thjesht duke i 
vÃ«nÃ« gjoksin njÃ« akti tÃ« lig. Kuptova qÃ« qenÃ« ndÃ«shkuar paq, ngaqÃ« 
kishin ngecur nÃ« rrjetÃ«n e konkurrencÃ«s, e cila nuk do tÃ« largohej apo 
tretej<a href=\"#foot-6\">(6)</a>. NdÃ«rkohÃ«, kish ardhur koha tÃ« fillohej 
ndÃ«rtimi i njÃ« bashkÃ«sie tÃ« re pÃ«r tÃ« zÃ«vendÃ«suar atÃ« qÃ« veprimet e 
tyre dhe tÃ« tjera e zhdukÃ«n."
+
+# type: Content of: <p>
+msgid "The Lisp community in the 70s was not limited to the <abbr>MIT</abbr> 
AI Lab, and the hackers were not all at <abbr>MIT</abbr>. The war that 
Symbolics started was what wiped out <abbr>MIT</abbr>, but there were other 
events going on then. There were people giving up on cooperation and together, 
this wiped out the community and there wasn't much left."
+msgstr "BashkÃ«sia Lisp nÃ« vitet '70 nuk kufizohej te <abbr>MIT</abbr> AI 
Lab, dhe <i>hacker</i>-at nuk qenÃ« vetÃ«m nÃ« <abbr>MIT</abbr>. Lufta e nisur 
nga Symbolics qe ajo qÃ« asgjÃ«soi <abbr>MIT</abbr>, por ndodhÃ«n dhe ngjarje 
tÃ« tjera. Pati persona qÃ« hoqÃ«n dorÃ« nga  bashkÃ«punimi, dhe kjo i vuri 
shkelmin bashkÃ«sisÃ« e kÃ«shtu nuk mbeti kushedi Ã§Ã«."
+
+# type: Content of: <p>
+msgid "Once I stopped punishing Symbolics, I had to figure out what to do 
next. I had to make a free operating system, that was clear &mdash; the only 
way that people could work together and share was with a free operating system."
+msgstr "Pasi reshta sÃ« ndÃ«shkuari Symbolics-in, mÃ« desh tÃ« gjeja se Ã§'tÃ« 
bÃ«ja mÃ« tej. Duhej tÃ« bÃ«jÃ« njÃ« sistem operativ tÃ« lirÃ«, qÃ« tÃ« qe i 
kthjellÃ«t &mdash; e vetmja mÃ«nyrÃ« qÃ« njerÃ«zit tÃ« mund tÃ« punonin tok dhe 
tÃ« shkÃ«mbenin qe pÃ«rmes njÃ« sistemi operativ tÃ« lirÃ«."
+
+# type: Content of: <p>
+msgid "At first, I thought of making a Lisp-based system, but I realized that 
wouldn't be a good idea technically. To have something like the Lisp machine 
system, you needed special purpose microcode. That's what made it possible to 
run programs as fast as other computers would run their programs and still get 
the benefit of typechecking. Without that, you would be reduced to something 
like the Lisp compilers for other machines. The programs would be faster, but 
unstable. Now that's okay if you're running one program on a timesharing system 
&mdash; if one program crashes, that's not a disaster, that's something your 
program occasionally does. But that didn't make it good for writing the 
operating system in, so I rejected the idea of making a system like the Lisp 
machine."
+msgstr "Fillimisht, pata nÃ« mendje tÃ« bÃ«ja njÃ« sistem tÃ« bazuar nÃ« Lisp, 
por e kuptova qÃ« nuk do tÃ« ishte ide e mirÃ« teknikisht. PÃ«r tÃ« pasur 
diÃ§ka tÃ« ngjashme me njÃ« sistem makine Lisp, ju duhet mikrokod pÃ«r qÃ«llime 
speciale. Ky qe ai qÃ« bÃ«nte tÃ« mundur xhirim po aq tÃ« shpejtÃ« sa xhironin 
kompjuterÃ«t e tjerÃ« programet e tyre dhe prapÃ« tÃ« kish pÃ«rparÃ«sinÃ« e 
kontrollit mbi llojin e tÃ« dhÃ«nave. Pa kÃ«tÃ«, do tÃ« pÃ«rfundonit nÃ« diÃ§ka 
tÃ« ngjashme me njÃ« pÃ«rpilues Lisp pÃ«r makina tÃ« tjera. Programet do tÃ« 
bÃ«heshin mÃ« tÃ« shpejta, por tÃ« paqÃ«ndrueshme. Me kÃ«tÃ« nuk ka problem, 
nÃ«se po xhironi njÃ« program nÃ« njÃ« sistem me ndarje kohe &mdash; nÃ«se 
vithiset njÃ« program, nuk u bÃ« hataja, Ã«shtÃ« diÃ§ka qÃ« ndodh te programet, 
me raste. Por kjo nuk e bÃ«nte tÃ« mirÃ« pÃ«r shkrimin e njÃ« sistemi operativ, 
ndaj e hodha poshtÃ« idenÃ« e krijimit tÃ« njÃ« sistemi si njÃ« njÃ« makinÃ« 
Lisp."
+
+# type: Content of: <p>
+msgid "I decided instead to make a Unix-like operating system that would have 
Lisp implementations to run as user programs. The kernel wouldn't be written in 
Lisp, but we'd have Lisp. So the development of that operating system, the GNU 
operating system, is what led me to write the GNU Emacs. In doing this, I aimed 
to make the absolute minimal possible Lisp implementation. The size of the 
programs was a tremendous concern."
+msgstr "Vendosa mÃ« mirÃ« tÃ« bÃ«ja njÃ« sistem operativ tÃ« ngjashÃ«m me 
Unix-in, qÃ« do tÃ« kishte sendÃ«rtime Lisp qÃ« do tÃ« xhironin si programe 
pÃ«rdoruesi. Kerneli nuk do tÃ« shkruhej nÃ« Lisp, por do tÃ« kishim Lisp. Dhe 
hartimi i kÃ«tij sistemi operativ, sistemit operativ GNU, qe ai qÃ« mÃ« shpuri 
te shkrimi i GNU Emacs-it. Duke bÃ«rÃ« kÃ«shtu, synoja tÃ« kryeja minimumin 
absolut tÃ« mundshÃ«m tÃ« sendÃ«rtimeve Lisp. MadhÃ«sia e programeve qe 
shqetÃ«sim shumÃ« i madh."
+
+# type: Content of: <p>
+msgid "There were people in those days, in 1985, who had one-megabyte machines 
without virtual memory. They wanted to be able to use GNU Emacs. This meant I 
had to keep the program as small as possible."
+msgstr "Kish njerÃ«z nÃ« ato kohÃ«, mÃ« 1985, qÃ« kishin makina me 1Mb 
kujtesÃ«, pa kujtesÃ« virtuale. Donin tÃ« ishin nÃ« gjendje tÃ« pÃ«rdornin GNU 
Emacs. Kjo do tÃ« thoshte ta mbaja programin sa mÃ« tÃ« vogÃ«l qÃ« mundej."
+
+# type: Content of: <p>
+msgid "For instance, at the time the only looping construct was 
&lsquo;while&rsquo;, which was extremely simple. There was no way to break out 
of the &lsquo;while&rsquo; statement, you just had to do a catch and a throw, 
or test a variable that ran the loop. That shows how far I was pushing to keep 
things small. We didn't have &lsquo;caar&rsquo; and &lsquo;cadr&rsquo; and so 
on; &ldquo;squeeze out everything possible&rdquo; was the spirit of GNU Emacs, 
the spirit of Emacs Lisp, from the beginning."
+msgstr "PÃ«r shembull, nÃ« atÃ« kohÃ« e vetmja strukturÃ« ripÃ«rsÃ«ritÃ«se qe 
&lsquo;while&rsquo;, e cila qe fare e thjeshtÃ«. Nuk kish mÃ«nyrÃ« pÃ«r tÃ« 
dalÃ« nga deklarimi &lsquo;while&rsquo;, ju duhej tÃ« kryenit \"a catch and a 
throw\", ose tÃ« testonit ndryshoren qÃ« xhironte ripÃ«rsÃ«ritjen. Kjo tregon 
se sa larg isha shtyrÃ« pÃ«r t'i mbajtur gjÃ«rat tÃ« vogla. Nuk kishte 
&lsquo;automjeet&rsquo; dhe as &lsquo;atomjet&rsquo; e me radhÃ«; 
&ldquo;ngjeshe sa tÃ« mundet&rdquo; qe fryma e GNU Emacs-it, fryma e Lisp-it 
pÃ«r Emacs, qÃ« nÃ« fillim."
+
+# type: Content of: <p>
+msgid "Obviously, machines are bigger now, and we don't do it that way 
anymore. We put in &lsquo;caar&rsquo; and &lsquo;cadr&rsquo; and so on, and we 
might put in another looping construct one of these days. We're willing to 
extend it some now, but we don't want to extend it to the level of common Lisp. 
I implemented Common Lisp once on the Lisp machine, and I'm not all that happy 
with it. One thing I don't like terribly much is keyword arguments. They don't 
seem quite Lispy to me; I'll do it sometimes but I minimize the times when I do 
that."
+msgstr "E qartÃ«, sot makinat janÃ« mÃ« tÃ« mÃ«dhaja, dhe nuk veprojmÃ« mÃ« 
kÃ«shtu. VÃ«mÃ« edhe &lsquo;automjeet&rsquo;, edhe &lsquo;atomjet&rsquo; e me 
radhÃ«, dhe sot mundemi tÃ« vendosim edhe strukturÃ« tjetÃ«r ripÃ«rtÃ«ritÃ«se. 
Duam ta zgjerojmÃ« diÃ§ka, por nuk duam ta zgjerojmÃ« deri nÃ« shkallÃ«n e njÃ« 
Lisp-i tÃ« zakonshÃ«m. NjÃ«herÃ«, sendÃ«rtova Common Lisp nÃ« makinÃ«n Lisp, 
dhe nuk mÃ« kÃ«naqi kushedi. DiÃ§ka qÃ« nuk mÃ« pÃ«lqen dhe aq shumÃ« janÃ« 
argumentat fjalÃ«kyÃ§a. Nuk mÃ« duken edhe aq tÃ« stilit Lisp; Do t'i ndÃ«rroj 
ndonjÃ« ditÃ«, por minimizoj kohÃ«t kur bÃ«j kÃ«shtu."
+
+# type: Content of: <p>
+msgid "That was not the end of the GNU projects involved with Lisp. Later on 
around 1995, we were looking into starting a graphical desktop project. It was 
clear that for the programs on the desktop, we wanted a programming language to 
write a lot of it in to make it easily extensible, like the editor. The 
question was what it should be."
+msgstr "Ky nuk qe fundi i projekteve GNU qÃ« kishin tÃ« bÃ«nin me Lisp-in. MÃ« 
vonÃ«, diku aty nga 1995, po shihnim mundÃ«sinÃ« e fillimit tÃ« njÃ« projekti 
pÃ«r njÃ« desktop grafik. Qe e qartÃ« qÃ«, pÃ«r programet nÃ« desktop, donim 
njÃ« gjuhÃ« programimi me tÃ« cilÃ«n tÃ« shkruanim shumÃ« dhe tÃ« qe 
lehtÃ«sisht e zgjerueshme, njÃ«soj si pÃ«rpunuesi. ÃÃ«shtja qe se cila duhej 
zgjedhur."
+
+# type: Content of: <p>
+msgid "At the time, <acronym title=\"Tool Command Language\">TCL</acronym> was 
being pushed heavily for this purpose. I had a very low opinion of 
<acronym>TCL</acronym>, basically because it wasn't Lisp. It looks a tiny bit 
like Lisp, but semantically it isn't, and it's not as clean.  Then someone 
showed me an ad where Sun was trying to hire somebody to work on 
<acronym>TCL</acronym> to make it the &ldquo;de-facto standard extension 
language&rdquo; of the world. And I thought, &ldquo;We've got to stop that from 
happening.&rdquo; So we started to make Scheme the standard extensibility 
language for GNU. Not Common Lisp, because it was too large. The idea was that 
we would have a Scheme interpreter designed to be linked into applications in 
the same way <acronym>TCL</acronym> was linked into applications. We would then 
recommend that as the preferred extensibility package for all GNU programs."
+msgstr "NÃ« atÃ« kohÃ«, <acronym title=\"Tool Command Language\">TCL</acronym> 
po reklamohej rÃ«ndshÃ«m pÃ«r kÃ«tÃ« qÃ«llim. Kisha velrÃ«sim shumÃ« tÃ« ulÃ«t 
pÃ«r <acronym>TCL</acronym>-nÃ«, pikÃ«sÃ«pari ngaqÃ« nuk qe Lisp. Ngjante 
pakÃ«z me Lisp-in, por semantikisht nuk qe e tillÃ«, dhe nuk Ã«shtÃ« aq i 
qÃ«ruar.  Mandej dikush mÃ« tregoi njÃ« lajmÃ«rim me tÃ« cilin Sun po pÃ«rpiqej 
tÃ« punÃ«sonte dikÃ« pÃ«r t'u marrÃ« me <acronym>TCL</acronym> pÃ«r ta bÃ«rÃ« 
&ldquo;standardin de-facto pÃ«r gjuhÃ« zgjerimesh&rdquo; nÃ« botÃ«. Dhe 
mendova, &ldquo;Duhet ta ndalim pÃ«rmbushjen e kÃ«saj.&rdquo; KÃ«shtu filluam 
tÃ« ndÃ«rtojmÃ« Scheme-n, gjuha standard e zgjerimeve pÃ«r GNU-nÃ«. Jo Common 
Lisp, ngaqÃ« ky qe shumÃ« i madh. Ideja qe qÃ« tÃ« kishim njÃ« interpretues 
Scheme tÃ« hartuar pÃ«r t'u lidhur te zbatimet nÃ« tÃ« njÃ«jtÃ«n mÃ«nyrÃ« si 
lidhej <acronym>TCL</acronym>-ja te zbatimet. Mandej kÃ«tÃ« ta kÃ«shillonim si 
paketÃ«n e parapÃ«lqyer pÃ«r zgjerime pÃ«r krejt programet GNU."
+
+# type: Content of: <p>
+msgid "There's an interesting benefit you can get from using such a powerful 
language as a version of Lisp as your primary extensibility language.  You can 
implement other languages by translating them into your primary language. If 
your primary language is <acronym>TCL</acronym>, you can't very easily 
implement Lisp by translating it into <acronym>TCL</acronym>. But if your 
primary language is Lisp, it's not that hard to implement other things by 
translating them. Our idea was that if each extensible application supported 
Scheme, you could write an implementation of <acronym>TCL</acronym> or Python 
or Perl in Scheme that translates that program into Scheme. Then you could load 
that into any application and customize it in your favorite language and it 
would work with other customizations as well."
+msgstr "Ka njÃ« pÃ«rfitim interesant qÃ« ju vjen nga pÃ«rdorimi i njÃ« gjuhe 
kaq tÃ« fuqishme siÃ§ do tÃ« ishte njÃ« version Lisp-i, si gjuhÃ«n tuaj 
parÃ«sore pÃ«r zgjerime.  Mund tÃ« sendÃ«rtoni gjuhÃ« tÃ« tjera, pÃ«rmes 
pÃ«rkthimit tÃ« tyre nÃ« gjuhÃ«n tuaj parÃ«sore. NÃ«se gjuha juaj parÃ«sore 
Ã«shtÃ« <acronym>TCL</acronym>, nuk sendÃ«rtoni dot lehtÃ« Lisp-in duke e 
pÃ«rkthyer nÃ« <acronym>TCL</acronym>. Por nÃ«se gjuha juaj parÃ«sore Ã«shtÃ« 
Lisp-i, nuk Ã«shtÃ« aq e zorshme tÃ« sendÃ«rtohen gjÃ«ra tÃ« tjera duke i 
pÃ«rkthyer ato. Ideja jonÃ« qe qÃ«, nÃ«se Ã§do zbatim i zgjerueshÃ«m mbulonte 
Scheme-n, mund tÃ« shkruanit nÃ« Scheme njÃ« sendÃ«rtim tÃ« 
<acronym>TCL</acronym>-sÃ«, ose Python-it, ose Perl-it, i cili ta pÃ«rkthente 
atÃ« program nÃ« Scheme. Mandej mund ta ngarkonit kÃ«tÃ« nÃ« Ã§farÃ«do zbatimi 
dhe ta pÃ«rshtasnit nÃ« gjuhÃ«n tuaj tÃ« parapÃ«lqyer dhe do tÃ« funksiononte 
edhe me pÃ«rshtatje tÃ« tjera."
+
+# type: Content of: <p>
+msgid "As long as the extensibility languages are weak, the users have to use 
only the language you provided them. Which means that people who love any given 
language have to compete for the choice of the developers of applications 
&mdash; saying &ldquo;Please, application developer, put my language into your 
application, not his language.&rdquo; Then the users get no choices at all 
&mdash; whichever application they're using comes with one language and they're 
stuck with [that language]. But when you have a powerful language that can 
implement others by translating into it, then you give the user a choice of 
language and we don't have to have a language war anymore. That's what we're 
hoping &lsquo;Guile&rsquo;, our scheme interpreter, will do. We had a person 
working last summer finishing up a translator from Python to Scheme. I don't 
know if it's entirely finished yet, but for anyone interested in this project, 
please get in touch. So that's the plan we have for the future."
+msgstr "PÃ«r sa kohÃ« qÃ« gjuhÃ«t e zgjerimeve janÃ« tÃ« dobÃ«ta, pÃ«rdoruesit 
i mbetet tÃ« pÃ«rdorÃ« vetÃ«m gjuhÃ«n qÃ« i jepni. QÃ« do tÃ« thotÃ« se 
njerÃ«zve qÃ« dashurojnÃ« cilÃ«ndo gjuhÃ« tjetÃ«r iu duhet tÃ« konkurrojnÃ« 
pÃ«r tÃ« qenÃ« ajo zgjedhja e hartuesve tÃ« zbatimeve &mdash; duke thÃ«nÃ« 
&ldquo;Ju lutem, hartues i zbatimit, vendoseni dhe gjuhÃ«n time te zbatimi 
juaj, jo gjuhÃ«n e atij.&rdquo; KÃ«shtu pÃ«rdoruesve nuk u lihet shteg zgjedhje 
fare &mdash; cilido zbatim qÃ« pÃ«rdorin, vjen me njÃ« gjuhÃ« dhe ngecin nÃ« 
tÃ« [atÃ« gjuhÃ«]. Por kur keni njÃ« gjuhÃ« tÃ« fuqishme qÃ« mund tÃ« 
sendÃ«rtojÃ« tÃ« tjerat pÃ«rmes pÃ«rkthimit tÃ« tyre nÃ« tÃ«, i jepni kÃ«shtu 
pÃ«rdoruesit njÃ« mundÃ«si zgjedhje gjuhe dhe nuk ka mÃ« pse tÃ« bÃ«jmÃ« mÃ« 
luftÃ« gjuhÃ«sh. Kjo Ã«shtÃ« ajo qÃ« shpresojmÃ« tÃ« bÃ«jÃ« 
&lsquo;Guile&rsquo;, interpretuesi ynÃ« Scheme. Kishim dikÃ« qÃ« punoi verÃ«n e 
shkuar pÃ«r tÃ« pÃ«rfunduar njÃ« pÃ«rkthyes nga Python nÃ« Scheme. Nuk e di 
nÃ«se ka pÃ«rfunduar krejtÃ«sisht, por cilido i interesuar pÃ«r kÃ«tÃ« projekt, 
ju lutem, le tÃ« lidhet me ta. Pra ky Ã«shtÃ« plani qÃ« kemi pÃ«r tÃ« ardhmen."
+
+# type: Content of: <p>
+msgid "I haven't been speaking about free software, but let me briefly tell 
you a little bit about what that means. Free software does not refer to price; 
it doesn't mean that you get it for free. (You may have paid for a copy, or 
gotten a copy gratis.) It means that you have freedom as a user. The crucial 
thing is that you are free to run the program, free to study what it does, free 
to change it to suit your needs, free to redistribute the copies of others and 
free to publish improved, extended versions. This is what free software means. 
If you are using a non-free program, you have lost crucial freedom, so don't 
ever do that."
+msgstr "S'kam folur pÃ«r <em>software</em>-in e lirÃ«, por mÃ« lejoni shkurt 
t'ju tregoj paksa se Ã§farÃ« don tÃ« thotÃ«. <em>Software</em> i lirÃ« nuk 
nÃ«nkupton Ã§mimin; nuk do tÃ« thotÃ« qÃ« e merrni falas. (Mundet edhe tÃ« 
paguani pÃ«r njÃ« kopje, ose tÃ« siguroni njÃ« kopje gratis.) Don tÃ« thotÃ« 
qÃ« keni liri, si pÃ«rdorues. GjÃ«ja kyÃ§e Ã«shtÃ« fakti qÃ« jeni i lirÃ« ta 
xhironi programin, i lirÃ« tÃ« studioni se Ã§farÃ« kryen, i lirÃ« ta ndryshoni 
qÃ« tÃ« pÃ«rputhet me nevojat tuaja, i lirÃ« tÃ« rishpÃ«rndani kopje pÃ«r tÃ« 
tjerÃ«t dhe i lirÃ« pÃ«r tÃ« bÃ«rÃ« publike versione tÃ« ndryshuara, tÃ« 
zgjeruara. Ky Ã«shtÃ« kuptimi i <em>software</em>-it tÃ« lirÃ«. NÃ«se pÃ«rdorni 
programe jo tÃ« lira, keni humbur liri kyÃ§e, ndaj me e bÃ«ni kurrÃ«."
+
+# type: Content of: <p>
+msgid "The purpose of the GNU project is to make it easier for people to 
reject freedom-trampling, user-dominating, non-free software by providing free 
software to replace it. For those who don't have the moral courage to reject 
the non-free software, when that means some practical inconvenience, what we 
try to do is give a free alternative so that you can move to freedom with less 
of a mess and less of a sacrifice in practical terms. The less sacrifice the 
better. We want to make it easier for you to live in freedom, to cooperate."
+msgstr "QÃ«llimi i projektit GNU Ã«shtÃ« t'ua bÃ«jÃ« mÃ« tÃ« lehtÃ« njerÃ«zve 
kundÃ«rshtimin e <em>software</em>-it jo tÃ« lirÃ«, i cili shtyp lirinÃ«, e 
sundon pÃ«rdoruesin, duke u ofruar atyre <em>software</em> tÃ« lirÃ« pÃ«r 
zÃ«vendÃ«sim. PÃ«r ata qÃ« nuk kanÃ« kurajo morale tÃ« hedhin tej 
<em>software</em>-in jo tÃ« lirÃ«, kur kjo sjell ca minuse nÃ« leverdinÃ« 
praktike, ajo qÃ« pÃ«rpiqemi tÃ« bÃ«jmÃ« Ã«shtÃ« dhÃ«nia e alternativave tÃ« 
lira, qÃ« kÃ«shtu tÃ« mund tÃ« shkoni drejt lirisÃ« me mÃ« pak belara dhe me 
mÃ« pak sakrifica, pÃ«rsa i takon anÃ«s praktike. Sa mÃ« pak sakrifica, aq mÃ« 
mirÃ«. Duam t'ua bÃ«jmÃ« mÃ« tÃ« lehtÃ« kalimin nÃ« liri, nÃ« bashkÃ«punim."
+
+# type: Content of: <p>
+msgid "This is a matter of the freedom to cooperate. We're used to thinking of 
freedom and cooperation with society as if they are opposites. But here they're 
on the same side. With free software you are free to cooperate with other 
people as well as free to help yourself. With non-free software, somebody is 
dominating you and keeping people divided. You're not allowed to share with 
them, you're not free to cooperate or help society, anymore than you're free to 
help yourself.  Divided and helpless is the state of users using non-free 
software."
+msgstr "KÃ«tu bÃ«het fjalÃ« pÃ«r lirinÃ« pÃ«r tÃ« bashkÃ«punuar. Jemi mÃ«suar 
t'i mendojmÃ« lirinÃ« dhe bashkÃ«punimin me shoqÃ«rinÃ« si tÃ« jenÃ« tÃ« 
kundÃ«rta. Por kÃ«tu janÃ« nÃ« tÃ« njÃ«jtin krah. Me <em>software</em>-in e 
lirÃ« jeni i lirÃ« tÃ« bashkÃ«punoni me tÃ« tjerÃ«t, si dhe i lirÃ« tÃ« 
ndihmoni vetveten. Me <em>software</em>-in jo tÃ« lirÃ«, dikush ju sundon dhe i 
mban njerÃ«zit tÃ« pÃ«rÃ§arÃ«. Nuk ju lejojnÃ« tÃ« shkÃ«mbeni mes jush, nuk 
jeni i lirÃ« tÃ« bashkÃ«punoni ose tÃ« ndihmoni shoqÃ«rinÃ«, dhe as tÃ« 
ndihmoni vetveten.  TÃ« pÃ«rÃ§arÃ« dhe tÃ« pashpresÃ« Ã«shtÃ« gjendja e 
pÃ«rdoruesve qÃ« pÃ«rdorin <em>software</em> jo tÃ« lirÃ«."
+
+# type: Content of: <p>
+msgid "We've produced a tremendous range of free software. We've done what 
people said we could never do; we have two operating systems of free software. 
We have many applications and we obviously have a lot farther to go. So we need 
your help. I would like to ask you to volunteer for the GNU project; help us 
develop free software for more jobs. Take a look at <a 
href=\"/help/\">http://www.gnu.org/help</a> to find suggestions for how to 
help. If you want to order things, there's a link to that from the home page. 
If you want to read about philosophical issues, look in /philosophy. If you're 
looking for free software to use, look in /directory, which lists about 1900 
packages now (which is a fraction of all the free software out there). Please 
write more and contribute to us. My book of essays, &ldquo;Free Software and 
Free Society&rdquo;, is on sale and can be purchased at <a 
href=\"http://www.gnu.org/\";>www.gnu.org</a>. Happy hacking!"
+msgstr "Kemi prodhuar njÃ« segment marramendÃ«s <em>software</em>-i tÃ« lirÃ«. 
Kemi bÃ«rÃ« ato qÃ« njerÃ«zit thoshin se nuk do t'ia dilnim t'i bÃ«nim kurrÃ«; 
kemi dy sisteme operativÃ« <em>software</em>-i tÃ« lirÃ«. Kemi mjaft zbatime 
dhe, kuptohet, kemi ende plot rrugÃ« pÃ«r tÃ« bÃ«rÃ«. Ndaj na duhet ndihma 
juaj. Do tÃ« doja t'ju kÃ«rkoja tÃ« merrni pjesÃ« si vullnetar nÃ« projektin 
GNU; na ndihmoni qÃ« tÃ« hartojmÃ« <em>software</em> tÃ« lirÃ« pÃ«r mÃ« shumÃ« 
punÃ«ra. Hidhini njÃ« sy <a href=\"/help/\">http://www.gnu.org/help</a> pÃ«r 
tÃ« pasur njÃ« ide se si mund tÃ« ndihmohet. NÃ«se dÃ«shironi tÃ« porosisni 
gjÃ«ra, ka njÃ« lidhje pÃ«r kÃ«tÃ« punÃ«, te faqja hyrÃ«se. NÃ«se doni tÃ« 
lexoni rreth Ã§Ã«shtjesh filozofike, shihni te ndarja /filozofi. NÃ«s po 
kÃ«rkoni <em>software</em>-e tÃ« lirÃ« qÃ« mund t'i pÃ«rdorni, shihni te 
/directory, ku sot radhiten gati 1900 paketa (Ã§ka Ã«shtÃ« vetÃ«m njÃ« pjesÃ« e 
<em>software</em>-eve tÃ« lirÃ«). Ju lutem na shkruani mÃ« tepÃ«r dhe 
kontribuoni me ne. Libri im me sprova, &ldquo;Free Software and Free 
Society&rdquo;, gjendet nÃ« shitje dhe mund tÃ« blihet te <a 
href=\"http://www.gnu.org/\";>www.gnu.org</a>. Happy hacking!"
+
+# type: Content of: <ol><li>
+msgid "Greenblatt's plan, as I understood it, was to hire lab people part 
time, so that they could continue working at the AI Lab.  Symbolics hired them 
full time instead, so they stopped working at MIT."
+msgstr "Plani i Greenblatt-it, si e kuptoja unÃ«, qe tÃ« punÃ«soheshin me 
kohÃ« tÃ« pjesshme njerÃ«z tÃ« laboratorit, qÃ« kÃ«shtu tÃ« mund tÃ« vazhdonin 
tÃ« punonin te AI Lab.  NÃ« vend tÃ« kÃ«saj, Symbolics i punÃ«soi me kohÃ« tÃ« 
plotÃ«, kÃ«shtu qÃ« kÃ«ta reshtÃ«n sÃ« punuari nÃ« MIT."
+
+# type: Content of: <ol><li>
+msgid "It was not that I cared particularly about the fate of LMI, but rather 
I did not want to let Symbolics gain through its aggression against the AI Lab."
+msgstr "Jo se mÃ« dhimbsej veÃ§anÃ«risht fati i LMI-Ã«, mÃ« tepÃ«r ngaqÃ« nuk 
doja qÃ« tÃ« lejohej Symbolics tÃ« pÃ«rfitonte nÃ« kurriz tÃ« AI Lab-it me 
agresionin e vet."
+
+# type: Content of: <ol><li>
+msgid "This statement has been misconstrued as saying that I never, ever 
looked at Symbolics' code.  Actually it says I did."
+msgstr "Ky pohim Ã«shtÃ« keqkuptuar sikur thotÃ« qÃ« unÃ« kurrÃ« nuk kam parÃ« 
te kodi i Symbolics-it. NÃ« fakt pohon qÃ« kisha parÃ« nÃ« tÃ«."
+
+# type: Content of: <ol><li><p>
+msgid "The Symbolics source code was available at MIT, where I was entitled to 
read it, and at first that's how I found out about their changes.  But that 
meant I had to make extra effort to solve each problem differently, in order to 
avoid copying Symbolics code.  After a while, I concluded it was better not to 
even look.  That way I could write code in whatever way was best, without 
concern for what was in Symbolics' code."
+msgstr "Kodi burim i Symbolics-it mund tÃ« shihej nÃ« MIT, ku edhe mÃ« lejohej 
ta shihja, dhe kÃ«shtu mora vesh sÃ« pari rreth ndryshimeve prej tyre.  Por kjo 
do tÃ« thoshte qÃ« duhej tÃ« bÃ«ja pÃ«rpjekje shtesÃ« pÃ«r ta zgjidhur ndryshe 
Ã§do problem, me qÃ«llim qÃ« tÃ« shmangja kopjimin e kodit tÃ« Symbolics-it.  
Pas ca kohÃ«sh, pashÃ« se qe mÃ« mirÃ« tÃ« mos shihje fare.  NÃ« kÃ«tÃ« 
mÃ«nyrÃ« mund tÃ« shkruaja kod sipas rrugÃ«s mÃ« tÃ« mirÃ«, pa vrarÃ« mendjen 
se Ã§'pÃ«rmbante kodi i Symbolics-it."
+
+# type: Content of: <ol><li>
+msgid "The background of this plan, which I did not state explicitly in the 
talk, is that during an initial period the ex-AI-Lab hackers, whether at 
Symbolics or LMI, continued contributing their changes to the MIT Lisp Machine 
system &mdash; even though the contract did not require this.  Symbolics' plan 
was to rupture this cooperation unilaterally."
+msgstr "Rrethanat e kÃ«tij plani, tÃ« cilat nuk i deklarova shprehimisht 
gjatÃ« fjalÃ«s sime, qenÃ« qÃ« gjatÃ« njÃ« periudhe fillestare <i>hacker</i>-at 
e ish-AI-Lab-it, ata nÃ« Symbolics ose ata nÃ« LMI, vazhduan t'i jepnin 
ndryshimet e tyre te sistemi MIT Lisp Machine &mdash; edhe pse kontrata nuk e 
detyronte kÃ«tÃ« hap.  Plani i Symbolics-it qe ta thyente njÃ«anÃ«sisht kÃ«tÃ« 
bashkÃ«punim."
+
+# type: Content of: <ol><li>
+msgid "Bernie Greenberg says that Dan Weinreb's implementation of Emacs for 
the Lisp Machine came before Greenberg's implementation for Multics.  I 
apologize for the mistake."
+msgstr "Bernie Greenberg thotÃ« se sendÃ«rtimi i Dan Weinreb-it pÃ«r Emacs nÃ« 
Lisp Machine kish dal para sendÃ«rtimit tÃ« Greenberg-ut pÃ«r Multics.  KÃ«rkoj 
ndjesÃ« pÃ«r gabimin."
+
+# type: Content of: <ol><li>
+msgid "Symbolics at one point protested to MIT that my work, by thwarting 
their plan, had cost Symbolics a million dollars."
+msgstr "Symbolics nÃ« njÃ« rast protestoi te MIT se puna ime, duke u prishur 
planin, i kish kushtuar Symbolics-it njÃ« milion dollarÃ«."
+
+# type: Content of: <ol><li>
+msgid "Guy Steele designed the original symmetrical Emacs command set; then he 
and I began implementing Emacs (on top of TECO), but after one long joint 
development session, Steele began drifting away, so I finished Emacs.  Others 
particularly including Eugene C. Cicciarelli and Mike McMahon contributed 
substantially later on."
+msgstr "Guy Steele hartoi grupin origjinal tÃ« komandave simetrike Emacs; 
mandej ai dhe unÃ« zumÃ« tÃ« vinim nÃ« jetÃ« Emacs-in (pÃ«rsipÃ«r TECO-s), por 
pas njÃ« sesioni tÃ« gjatÃ« programimi tÃ« pÃ«rbashkÃ«t, Steele-i zuri tÃ« 
rrÃ«shqiste tej, kÃ«shtu qÃ« Emacs-in e pÃ«rfundova unÃ«.  TÃ« tjerÃ«, pÃ«rfshi 
veÃ§anÃ«risht Eugene C. Cicciarelli-n dhe Mike McMahon-in, dhanÃ« ndihmesÃ« 
thelbÃ«sore mÃ« vonÃ«."
+
+# type: Content of: <div>
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr "  "
+
+# type: Content of: <div><p>
+msgid "Please send FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>.  There are also <a 
href=\"/contact/\">other ways to contact</a> the FSF.  <br /> Please send 
broken links and other corrections or suggestions to <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgstr "Ju lutem, pyetjet rreth FSF &amp; GNU dÃ«rgoji te <a 
href=\"mailto:address@hidden";><em>address@hidden</em></a>.  Ka gjithashtu edhe 
<a href=\"/contact/\">mÃ«nyra tÃ« tjera pÃ«r t'u lidhur me</a> FSF-nÃ«.  <br /> 
Ju lutem, lidhjet e dÃ«mtuara, kÃ«shillat dhe ndreqjet dÃ«rgojini te <a 
href=\"mailto:address@hidden";><em>address@hidden</em></a>."
+
+# type: Content of: <div><p>
+msgid "Please see the <a 
href=\"/server/standards/README.translations.html\">Translations README</a> for 
information on coordinating and submitting translations of this article."
+msgstr "PÃ«r tÃ« dhÃ«na mbi bashkÃ«rendimin dhe parashtrimin e pÃ«rkthimeve 
tÃ« kÃ«tij artikulli, ju lutem, shihni <a 
href=\"/server/standards/README.translations.html\">README pÃ«r 
pÃ«rkthimet</a>."
+
+# type: Content of: <div><p>
+msgid "Copyright &copy; 2003, 2007 Free Software Foundation, Inc."
+msgstr "TÃ« drejta kopjimi &copy; 2003, 2007 Free Software Foundation, Inc."
+
+# type: Content of: <div><p>
+msgid "Verbatim copying and distribution of this entire article is permitted 
in any medium, provided this notice is preserved."
+msgstr "Lejohet kopjimi fjalÃ« pÃ«r fjalÃ« dhe shpÃ«rndarja e krejt kÃ«tij 
artikulli,  me Ã§farÃ«do mjeti, pa pagesÃ«, me kusht qÃ« ky shÃ«nim tÃ« ruhet."
+
+# type: Content of: <div><div>
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
+msgstr " "
+
+# type: Content of: <div><p>
+#.  timestamp start
+msgid "Updated:"
+msgstr "PÃ«rditÃ«suar:"
+
+# type: Content of: <div><h4>
+msgid "Translations of this page"
+msgstr "PÃ«rkthime tÃ« kÃ«saj faqeje"
+
[Prev in Thread]
Current Thread
[Next in Thread]
www/gnu/po rms-lisp.sq.po, Besnik Bleta <=
Prev by Date: www/gnu/po initial-announcement.sq.po
Next by Date: www/server/standards/po webmaster-quiz.sq.po
Previous by thread: www/gnu/po initial-announcement.sq.po
Next by thread: www/server/standards/po webmaster-quiz.sq.po
Index(es):
- Date
- Thread