(from science 2.0)
"...To be told is to wallow in revealed truths. Bibles and similar religious texts are all about revealed truths which cannot be questioned, and the origins of which require the readers to make many assumptions. And it was even worse in the dark times of religious book control and illiteracy in which you might not even be allowed to read the book--you have to get the mediated verbal account from someone supposedly holier than you... Discovered truths, on the other hand, are not told. Of course somebody could tell you a discovered truth, but if you don't trust them you can question it. Discovered truths can be discussed. They can be questioned and tested.... "
Hit me the first time, when reading Wieland - or was it Lessing -. About believing without any question into a (badly written and communicated) narrative of things that happened thousand and some years ago.While having problems with the radio report on the rush hour ("...you just cant believe these dudes anymore...")
That's why my penchant for Sokrates: his middle name was curiousity.
ASK sauthon!
Mittwoch, 23. Februar 2011
Donnerstag, 8. Juli 2010
In a session on Verbatim, Pootle etc yesterday, Matjaz presented a Jetpack add-on, that allows one to use a translation memory (in a TMX form) during the Verbatim process. The example showed nicely, how one can take an existing TMX file, list the candidates (100% match and some fuzzies as well) and then drop the selection into the target segment.
Verbatim does not use any translation memory mechanism (as far as I know, not even MO, the nonstandard Pootle's version of a translation memory) to propagate the translations which already exist through the material to be translated. Well, fine, but then the JetPack solution by Matjaz will fix it, will it not?
Please note first, the TMX, to be used in the JetPack, comes from outside. It is not an integral part of the Verbatim / Pootle solution. It is a deus ex machina, a translational band-aid - for now at least, if not for some time coming.
Matjaz showed during the demo of his Jetpack solution, how "Australia" is translated into "Avstralija" with the help of an existing translation memory. Just before this example, however, there was a case of "Argentina" without any suggestion from TMX. Matjaz dropped in the copy of the source and then proceeded on to the next entry. But hold on a second: where did the target entry for "Argentina" land? Just in the PO? How adding the new stuff to TMX? After all it would not hurt to adhere to the Mozilla spirit and expand the TMX with the working being done. I am pretty certain, however, that in the case of Matjaz' add-on TMX get short-changed.
Here's the situation in a nutshell: external translational sources are tapped to (help Verbatim) help the localizer do the work. The Verbatim per se is not involved, as it does not as yet have any ways and means to tap into the possibilities, offered by standardized translation memories. On the other hand, the external sources are on receiving end of the stick in the Jetpack proposal, as their initial investment and the use of their assets, as implemented in the Matjaz' proposal, is not reciprocated by expanding the memory with new translations.
We all have open and free standards for everybody written all over our hearts, flags and banners. Standardized translation memory - free and open-sourced for all - must be among them.
Vito
PS: one of the listeners, who was evidently new to the subject of translation memories and specifically to the subject of TMX, commented with visible relief "Oh, fine, it's just an XML file". Oh well... XML file is not much, if anything at all, without a corresponding DTD.
To see DTD for TMX files - and implicitely all the work and drive behind it - see
TMX specification by LISA
Verbatim does not use any translation memory mechanism (as far as I know, not even MO, the nonstandard Pootle's version of a translation memory) to propagate the translations which already exist through the material to be translated. Well, fine, but then the JetPack solution by Matjaz will fix it, will it not?
Please note first, the TMX, to be used in the JetPack, comes from outside. It is not an integral part of the Verbatim / Pootle solution. It is a deus ex machina, a translational band-aid - for now at least, if not for some time coming.
Matjaz showed during the demo of his Jetpack solution, how "Australia" is translated into "Avstralija" with the help of an existing translation memory. Just before this example, however, there was a case of "Argentina" without any suggestion from TMX. Matjaz dropped in the copy of the source and then proceeded on to the next entry. But hold on a second: where did the target entry for "Argentina" land? Just in the PO? How adding the new stuff to TMX? After all it would not hurt to adhere to the Mozilla spirit and expand the TMX with the working being done. I am pretty certain, however, that in the case of Matjaz' add-on TMX get short-changed.
Here's the situation in a nutshell: external translational sources are tapped to (help Verbatim) help the localizer do the work. The Verbatim per se is not involved, as it does not as yet have any ways and means to tap into the possibilities, offered by standardized translation memories. On the other hand, the external sources are on receiving end of the stick in the Jetpack proposal, as their initial investment and the use of their assets, as implemented in the Matjaz' proposal, is not reciprocated by expanding the memory with new translations.
We all have open and free standards for everybody written all over our hearts, flags and banners. Standardized translation memory - free and open-sourced for all - must be among them.
Vito
PS: one of the listeners, who was evidently new to the subject of translation memories and specifically to the subject of TMX, commented with visible relief "Oh, fine, it's just an XML file". Oh well... XML file is not much, if anything at all, without a corresponding DTD.
To see DTD for TMX files - and implicitely all the work and drive behind it - see
TMX specification by LISA
Jetpack add-on for Verbatim
at Mozilla Summit 2010, 8.july
In a session on Verbatim, Pootle etc yesterday, Matjaz presented a Jetpack add-on, that allows one to use a translation memory (in a TMX form) during the Verbatim process. The example showed nicely, how one can take an existing TMX file, list the candidates (100% match and some fuzzies as well) and then drop the selection into the target segment.
Verbatim does not use any translation memory mechanism (as far as I know, not even MO, the nonstandard Pootle's version of a translation memory) to propagate the translations which already exist through the material to be translated. Well, fine, but then the JetPack solution by Matjaz will fix it, will it not?
Please note first, the TMX, to be used in the JetPack, comes from outside. It is not an integral part of the Verbatim / Pootle solution. It is a deus ex machina, a translational band-aid - for now at least, if not for some time coming.
Matjaz showed during the demo of his Jetpack solution, how "Australia" is translated into "Avstralija" with the help of an existing translation memory. Just before this example, however, there was a case of "Argentina" without any suggestion from TMX. Matjaz dropped in the copy of the source and then proceeded on to the next entry. But hold on a second: where did the target entry for "Argentina" land? Just in the PO? How adding the new stuff to TMX? After all it would not hurt to adhere to the Mozilla spirit and expand the TMX with the working being done. I am pretty certain, however, that in the case of Matjaz' add-on TMX get short-changed.
Here's the situation in a nutshell: external translational sources are tapped to (help Verbatim) help the localizer do the work. The Verbatim per se is not involved, as it does not as yet have any ways and means to tap into the possibilities, offered by standardized translation memories. On the other hand, the external sources are on receiving end of the stick in the Jetpack proposal, as their initial investment and the use of their assets, as implemented in the Matjaz' proposal, is not reciprocated by expanding the memory with new translations.
We all have open and free standards for everybody written all over our hearts, flags and banners. Standardized translation memory - free and open-sourced for all - must be among them.
Vito
PS: one of the listeners, who was evidently new to the subject of translation memories and specifically to the subject of TMX, commented with visible relief "Oh, fine, it's just an XML file". Oh well... XML file is not much, if anything at all, without a corresponding DTD.
To see DTD for TMX files - and implicitely all the work and drive behind it - see
TMX specification by LISA
In a session on Verbatim, Pootle etc yesterday, Matjaz presented a Jetpack add-on, that allows one to use a translation memory (in a TMX form) during the Verbatim process. The example showed nicely, how one can take an existing TMX file, list the candidates (100% match and some fuzzies as well) and then drop the selection into the target segment.
Verbatim does not use any translation memory mechanism (as far as I know, not even MO, the nonstandard Pootle's version of a translation memory) to propagate the translations which already exist through the material to be translated. Well, fine, but then the JetPack solution by Matjaz will fix it, will it not?
Please note first, the TMX, to be used in the JetPack, comes from outside. It is not an integral part of the Verbatim / Pootle solution. It is a deus ex machina, a translational band-aid - for now at least, if not for some time coming.
Matjaz showed during the demo of his Jetpack solution, how "Australia" is translated into "Avstralija" with the help of an existing translation memory. Just before this example, however, there was a case of "Argentina" without any suggestion from TMX. Matjaz dropped in the copy of the source and then proceeded on to the next entry. But hold on a second: where did the target entry for "Argentina" land? Just in the PO? How adding the new stuff to TMX? After all it would not hurt to adhere to the Mozilla spirit and expand the TMX with the working being done. I am pretty certain, however, that in the case of Matjaz' add-on TMX get short-changed.
Here's the situation in a nutshell: external translational sources are tapped to (help Verbatim) help the localizer do the work. The Verbatim per se is not involved, as it does not as yet have any ways and means to tap into the possibilities, offered by standardized translation memories. On the other hand, the external sources are on receiving end of the stick in the Jetpack proposal, as their initial investment and the use of their assets, as implemented in the Matjaz' proposal, is not reciprocated by expanding the memory with new translations.
We all have open and free standards for everybody written all over our hearts, flags and banners. Standardized translation memory - free and open-sourced for all - must be among them.
Vito
PS: one of the listeners, who was evidently new to the subject of translation memories and specifically to the subject of TMX, commented with visible relief "Oh, fine, it's just an XML file". Oh well... XML file is not much, if anything at all, without a corresponding DTD.
To see DTD for TMX files - and implicitely all the work and drive behind it - see
TMX specification by LISA
Freitag, 23. April 2010
lokalizacija = sl.jar
Če si v (zaenkrat shredder imenovani) instalaciji pogledaš podmapo chrome, boš naletel na datoteko sl.jar, ki vsebuje naše dosedanje delo. Lokalizacija ni nič več in nič manj kot vsebina te knjižnice.
Za novo verzijo je treba (samo in nič več kot to) novo verzijo sl.jar.
Francesco( mozilla l10n blog )
Za novo verzijo je treba (samo in nič več kot to) novo verzijo sl.jar.
Francesco( mozilla l10n blog )
You can simply download the latest nightly and work on the chrome/sl.jar of that package: if you're using Windows (but it's probaly possible for other platforms as well), you can use 7zip's File Manager and change files without unpacking/repacking the .jar file.Da vidimo ... 7Zip. Zap ... Ha!... dejansko.
Mittwoch, 3. März 2010
Prevodi vključeni v release proceduro
Oglasil se je Simon Paquet z lepo novico, da je prevode vdelal v sistem - gre za stanje, preden je Aleš R poslal zadnji delež. Tu dnevnik dosedanjih dogodkov
Stanje je videti na naslednjih naslovih:sl shipping 3.0 in sl shipping 3.1
Poleg manjkajočih delov je Simon omenil še naslednje: prevajali smo tudi zadeve, za katere je v komentarjih eksplicitno zahtevano, da se jih pusti pri miru. Moja krivda in v bodoče naloga, da skrbim za te primere.
Testbuild naj bi bil po njegovih besedah na razpolago enkrat danes: TB 3.0 oz. TB 3.1
Mercurial, skladišča, pošte ...
Sistem, ki se v Mozilli uporablja za hranjenje in ažuriranje izvorne kode, se imenuje Mercurial.
Kdor je doslej že delal z SVN ipd., se na Mercurial (ali kratko hg) lahko hitro navadi. Glede na to, da gre za prostokodne projekte, je pri Mozilli vse na dlani:
mozilla.org releases repository ... seveda za branje, za pisanje obstaja procedura, kako se do teh pravic pride.
Še en naslov: poštna stran za "lokalizatorje".
Lep pozdrav in upam da lepa novica za vse.
PS: Ali je mogoče komentirati?
Zaenkrat nobenih komentarjev ali prijavljencev na blog, pri čemer ne vem, ali je krivda nezanimiva ali nesporna vsebina, ali pa nastavitev bloga. Lahko kdo poizkusi s komentarjem?
Stanje je videti na naslednjih naslovih:sl shipping 3.0 in sl shipping 3.1
Poleg manjkajočih delov je Simon omenil še naslednje: prevajali smo tudi zadeve, za katere je v komentarjih eksplicitno zahtevano, da se jih pusti pri miru. Moja krivda in v bodoče naloga, da skrbim za te primere.
Testbuild naj bi bil po njegovih besedah na razpolago enkrat danes: TB 3.0 oz. TB 3.1
Mercurial, skladišča, pošte ...
Sistem, ki se v Mozilli uporablja za hranjenje in ažuriranje izvorne kode, se imenuje Mercurial.
Kdor je doslej že delal z SVN ipd., se na Mercurial (ali kratko hg) lahko hitro navadi. Glede na to, da gre za prostokodne projekte, je pri Mozilli vse na dlani:
mozilla.org releases repository ... seveda za branje, za pisanje obstaja procedura, kako se do teh pravic pride.
Še en naslov: poštna stran za "lokalizatorje".
Lep pozdrav in upam da lepa novica za vse.
PS: Ali je mogoče komentirati?
Zaenkrat nobenih komentarjev ali prijavljencev na blog, pri čemer ne vem, ali je krivda nezanimiva ali nesporna vsebina, ali pa nastavitev bloga. Lahko kdo poizkusi s komentarjem?
Sonntag, 28. Februar 2010
Izrazoslovje II, Google Docs, FOSDEM
attachment: priponka. Nasvet Aleša K, U.C idr. Izraz uporablja tudi Microsoftov glosar
offline mode: nepovezan način. Gre lepše z jezika in s tipkovnice kot način brez povezave.
Ker glosar vidno raste, sem ga postavil v Google Docs (EN SL (Mozilla) glosar). Tam je najti tudi preglednico s stanjem projekta - gl. privatno pošto s tem v zvezi -.
Kako odgovarjati na ta blog oz. ga komentirati? Da ne bi prihajalo do anonimk, vandalizma, se je treba prijaviti, potem pa bi moralo iti brez problemov.
Kaj je na sporedu?
Naslednji cilj je testna verzija, kjer bomo lahko videli, kaj vse je narobe (g). V tem smislu čakam na sporočilo kolegov pri Mozilli.
Zanimivo branje: Thunderbird_Localization
od tu se lahko zakrmari do naslednje strani, ki je merodajna: l10n dashboard/
Za konec spominek z letošnjega FOSDEM
The 2010 Fosdem dance
Lep pozdrav
smo
offline mode: nepovezan način. Gre lepše z jezika in s tipkovnice kot način brez povezave.
Ker glosar vidno raste, sem ga postavil v Google Docs (EN SL (Mozilla) glosar). Tam je najti tudi preglednico s stanjem projekta - gl. privatno pošto s tem v zvezi -.
Kako odgovarjati na ta blog oz. ga komentirati? Da ne bi prihajalo do anonimk, vandalizma, se je treba prijaviti, potem pa bi moralo iti brez problemov.
Kaj je na sporedu?
Naslednji cilj je testna verzija, kjer bomo lahko videli, kaj vse je narobe (g). V tem smislu čakam na sporočilo kolegov pri Mozilli.
Zanimivo branje: Thunderbird_Localization
od tu se lahko zakrmari do naslednje strani, ki je merodajna: l10n dashboard/
Za konec spominek z letošnjega FOSDEM
The 2010 Fosdem dance
Lep pozdrav
smo
Donnerstag, 25. Februar 2010
Izrazoslovje I
To, From, cc, bcc: Za, Od, Kp, Skp. Nisem prepričan glede Skp
junk mail: neželena pošta. Lepo bi bilo kaj bolj "udarnega".
attachment: priloga. Najti je tudi predlog pripetek, ne vem pa, ali se mu je uspelo udomačiti se.
certificate: potrdilo - brez digitalno. Glede na dolgoletne izkušnje Slovenije s certifikati je vprašanje, ali ima moj predlog smisel.
tbc
smo
junk mail: neželena pošta. Lepo bi bilo kaj bolj "udarnega".
attachment: priloga. Najti je tudi predlog pripetek, ne vem pa, ali se mu je uspelo udomačiti se.
certificate: potrdilo - brez digitalno. Glede na dolgoletne izkušnje Slovenije s certifikati je vprašanje, ali ima moj predlog smisel.
tbc
smo
Abonnieren
Posts (Atom)