?

Log in

No account? Create an account
LJ latviešu valodā
Pēdējie ieraksti 
18. janv.., 2006 20:23(nav temata)
dear diary
The pages that need translation (with severity 3) are shown here: http://lj.setia.ru/translate/lv/ It directly links to the editing interface. It seems it may be useful when you would like to translate all strings from a particular page.
28. dec.., 2005 21:17 - Vārdnica
dear diary
Visparīgie termini
Download Lejupielādēt ?
Form Forma *
Log in Ienākt ?
Log out Iziet ?
Rich Text editor Vizuālais redaktors/režīms *
Tags Marķieri *
Upload Augšupielādēt ?
Userpicture Lietotājattēls (ne bilde) *
Website Mājas lapa *
Lietotāji
User Lietotājs
Early Adopter Agrais Lietotājs ?
Lietotāja info
Friends of: Draugos: ?
Member of: Biedros: ?
Watched by: Lasītāji: *
Kopienas
Community Kopiena
Maintainer Uzturētājs *
Member Biedrs *


* - leads to an entry discussing translation of this word;
! - pay special attention;
? - means this word is not confirmed completely; if there is an entry discussing its translation, leads to it.

Comment if you feel something should be added. Based on lj_russian dictionary.
24. dec.., 2005 12:56(nav temata)
dear diary
Another word for which we should standardize translation: "Maintainer". I saw this previously discussed in this community here, and it was translated as "Uzturētājs". Now I also saw "Atbildīgie" on the Community information pages. I like the first better. The second has a meaning more like "responsible". Any other ideas?
1. dec.., 2005 19:35 - Announcement
dear diary
As the Latvian translators have become inactive, I've been temporarily assigned as the head of the Latvian translation team. I hope people don't mind me writing in English. I have edited the style of this community.

1. All the translators should join and watch lj_translate as well as this community in case of important announcements. It may also be useful to keep track of lj_userdoc, where any changes to the English documentation are noted. However, it has a relatively large volume of entries, and Latvian translation is so out of date that these may not be very helpful.

2. Translation Tutorial.

If you would like to help with translation, please read this entry and all other tagged "must read", then comment here saying you have read this and I will give you the privilege "translate:lv" allowing you to translate. I'm sorry, it's long, but it's important. It shows how to effectively use the tools too.

First of all, there is a Translation Area. This page lists all languages for which there are translation teams, with some information on the status of the translations. In particular, it currently shows that Latvian is about 12.90% done (completed 455 out of 3528 strings). It also shows the date someone last translated or edited Latvian translation.

The link from the word Latvian leads to the Language Editor interface. I have also added this link to the sidebar of the community, so that you may go directly from the community to it. You can view it even while you don't have any privs, but you will not be able to search strings or save any changes. It is important to understand how the Editor works. There are basically three sections in it: the top left corner, where you can search translation strings by certain criteria, the bottom left where the search results will appear, and the largest right section, where the text to be translated will appear.

Part I. Searching


The top left corner provides two search options. You cannot search by both at the same time.

a) By severity


It is very important to understand what severity is. Severity is a way to show how up-to-date the translation is, with 0 being the up-to-date translation, that has not been changed in the original since the translфtion, 1 and 2 meaning the original has changed somewhat and there's a need to re-translate possibly, 3 means that this is something new that was added and does not have a translation yet at all. I will return to this again a bit later.

You can search all translation strings that have a certain severity (by choosing one of the options 0, 1, 2, 3, 4) or all strings at and above a certain severity (0+, 1+, 2+, 3+). Normally, you can ignore severity 0, unless you come across a typo somewhere (but then it may be more useful to use the second search option described below). To translate everything new that doesn't have any translation yet, you may choose 3+.

While this option is very useful when the translation is almost complete, and you want to find new translation strings that may have been added, it is unhelpful in cases where you may have come across awkward translation, typo, etc. through your regular use of the site, and wish to correct it. That's when you might use the second option.

b) By text



The "Search" drop down menu has three options: "Latvian," "English (LJ)," and "Item Code." This is used to specify exactly what you would like to search. You can search the Latvian translation, the original English content, or the "item codes" of the translation strings.

Here's a random translation string, for example:


The English (LJ) and Latvian are pretty much self-explanatory. So I would like to point out a couple of things about the "item code." The item code of this translation string is "/allpics.bml.current". The first part "/allpics.bml" indicates the LiveJournal site address where this string may be found. Just insert http://www.livejournal.com before the slash (http://www.livejournal.com/allpics.bml). The second part is just a unique name assigned to that string to distinguish it from any other on that page.



As a quick sidenote, it is possible to view a page in a certain language even if you haven't selected it in your settings. You can do it by adding to the end of the link ?uselang= and the language code. For example, to view a page in Latvian, people may add ?uselang=lv (assuming the page was translated, of course); to view a page in original English, add ?uselang=en_LJ (must be capitalized in this way or it won't work). If the URL address already has a question mark, then you should use & instead.



And this aside leads to the following revelation: it is possible to determine the item code of a certain translation string by appending the link with ?uselang=debug Let's see for instance that same page as before in this mode: http://www.livejournal.com/allpics.bml?uselang=debug Note when you do this, only the ".current" part shows up, not the whole "/allpics.bml.current".

Okay, let's move on. The second drop-down menu "Area" has options "(all)," "general," "faq," and "journal/news." I'm not sure what "general" and "journal/news" are. I normally leave the area "(all)", except in cases when I want to limit the results to FAQs.

Then, you enter the text you wish to search for. The text that you should enter depends on what you have chosen in the "Search" drop-down.

Let's suppose that that string I used as an example earlier was translated into Latvian as "Esošas bildes," and you saw it and thought it should be corrected to "Esošās bildes." You could search for Latvian text (leaving the area as "all") and entering "Esošas bildes" in the text field (without quotes). Especially if you suspect that such a misspelling may be common and you'd like to see if there are other similar instances to correct. On the other hand, if this was a more common phrase and appeared multiple times in various places (legitimately), so that you can't find the one you need among the rest; you could instead look up the item code using the ?uselang=debug and search for an Item code and entering "allpics.bml" or ".current" etc. Sometimes, through your regular use of the site you may get an error message in English because it has not been translated yet, and you might like to translate it (and most likely you would not be able to use ?uselang=debug as an error message opens into a separate page, sort of); in that case, you could select English (LJ) and quote a small piece of an error message to find the translation string you need.

Part II. Search results


The lower left area shows the search results when you hit 'Search' in the upper area if you have the translation privileges for the language. If you don't, you will receive an error message instead. However, this area would show all the translation strings, and you could look at them without having the privilege yet.

You should see something like:



If the search results have over 10 translation strings there will be several pages, each page with 10 strings (the last one may have less). The strings will be listed alphabetically, and the search results will show the first and last string on a particular page. In the example above, on Page 1 the first translation string is "/accountstatus.bml.btn.status" and the last one is "/accountstatus.bml.journalstatus.select.deleted" (it cuts off on the picture I made because of length, but I could scroll and see it). On Page 3, the first string is "/allpics.bml.nopics.text.other" and the last is
"/approve.bml.error.approving".

Part III. Translating, or Editing.


Finally we come to the right side of the screen, where you actually translate or edit translations. When you click on the 'Page #' in your search results the translation strings appear in this part of the screen like the /allpics.bml.currrent I showed before.



Now we'll take a closer look again. At the top right corner you may notice words "Sev: 0". Sev here is the severity I talked about. Here it means that no changes were made to this string in the original since it was translated. For next example, I'll take a string that has Severity 2 (meaning the translation did change, and this needs editing).


Click for larger image


So this time, it says "Sev: 2". Another thing of note - there's now a link saying "diff". It links to a diff page - what has changed. (In this case it linked to http://www.livejournal.com/translate/diff.bml?it=1:723&lang=en_LJ)


Click for larger image


The diff page shows in pink words or phrases that were deleted, in green words and phrases that were added. Also if there were several changes, there will be links to the previous diff pages at the top: [Change 1] [Change 2] [Change 3] etc. So sometimes you may need to look back to see if these changes were already applied to the translation or not yet.

On this particular string, the changes were purely cosmetic (Change 1 corrected a typo, Change 2 turned the HTML code to lower case and reintroduced a typo, Change 3 corrected the typo again).

To actually edit text, put a checkmark in the Edit box, and do your thing ;) .



If the text hasn't been translated yet, just enter the translation in the provided field.

Then scroll down to the bottom of the page, and click Save.



If you don't have the translation privilege, the button will be unclickable.

5. sept.., 2002 15:38(nav temata)
Es ļoti palūgšu turpmāk, tulkojot LJ, ievērot oriģināla pieturzīmes, kā arī, un šis lūgums ir vēl būtiskāks, paskatīties kontekstu, lai tulkojumam būtu jēga.

Kā, piemēram, /userinfo.bml.label.nofriends, oriģinālā (angliski) < i >None listed.< / i >, latviski tas nebūs vis "Neviens no minētajiem", jo iet runa par (more details...) lapu userinfo, kur šis teikums parādās, ja lietotāja draugu sarakstā nav minēts neviens vārds.

Treškārt, lūdzu, lūdzu, ievērojiet HTML tags!!!!! Augšminētajā piemērā < i >... tos nekādā gadījumā nedrīkst atmest.
6. jūl.., 2002 17:56(nav temata)
Gribēju tikai pateikt, ka nupat esmu sasniegusi 30.75% LJ tulkošanā, kā to var redzēt šeit.
Vispār interesanti. Rezultātu pašās LJ lapās vēl nevar redzēt, nav ne jausmas, kad latviešu valoda tiks pievienota to valodu sarakstam, uz kurām var pārslēgties. Laikam būs kādam jāpajautā!
22. jūn.., 2002 17:29(nav temata)
Man jau radusies pirmā neskaidrība. Community members, vai tie būtu kopienas locekļi? Zināms, cik ļoti dažiem nepatīk vārds 'loceklis'......... Un 'membership'?
Maintainer account, pašlaik esmu pārtulkojusi kā 'uzturētāja konts', vai ir citi ieteikumi?
'Website', kā labāk - web lapa vai tīkla lapa?
21. jūn.., 2002 00:08(nav temata)
Iesākumā bija vārds. Un šis vārds bija LiveJournal.
Ar šo brīdi LJ tulkošana latviešu valodā ir sākusies.
Pašlaik autorizēti tulkot ir divi LJ lietotāji - es, pixie_lv un milzite. Ja kāds ir nejauši atklīdis vai apzināti atradis šo kopienu, pārvalda gan latviešu, gan angļu valodu un var ziedot dažas minūtes vai stundas sava laika, laipni lūdzam mūsu komandā.
This page was loaded nov. 24. 2017, 5:44 am GMT.