# Macedonian translation of [ www.linux.net.mk ]
# Copyright (c) 2005 Арангел Drupal allows you to translate the interface to a language other "
"than English. This page provides an overview of the installed "
"languages. You can add more languages on the add language page, or directly by importing a translation. If there are multiple "
"languages enabled, registered users will be able to set their "
"preference. The site default will be used for users without their own "
"settings, including anonymous visitors. There are different "
"approaches to translate the Drupal interface: either by importing an existing translation, by translating everything yourself, or by using a "
"combination of these. Most programs are written and documented in English, and "
"primarily use English to interact with users. This is also true for a "
"great deal of web sites. However, most people are less comfortable "
"with English than with their native language, and would prefer to use "
"their mother tongue as much as possible. Many people love to see their "
"web site showing a lot less English, and far more of their own "
"language. Therefore Drupal provides a framework to setup a "
"multi-lingual web site, or to overwrite the default English "
"texts. Whenever Drupal encounters an interface string which needs to "
"be displayed, it tries to translate it into the currently selected "
"language. If a translation is not available, then the string is "
"remembered, so you can look up untranslated strings easily. Drupal provides two options to translate these strings. First "
"is the integrated web interface, where you can search for untranslated "
"strings, and specify their translations via simple web forms. An "
"easier, and much less time consuming method is to import translations "
"already done for your language. This is achieved by the use of GNU "
"gettext Portable Object files. These are editable with quite "
"convinient desktop editors specifically architected for supporting "
"your work with GNU Gettext files. The import feature allows you to add "
"strings from such files into the site database. The export "
"functionality enables you to share your translations with others, "
"generating Portable Object files from your site strings."
msgstr ""
#: /~linuxnetmk/?q=admin/locale
msgid "[more help...]"
msgstr " [повеќе помош...]"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "Leave blank to show all strings. The search is case sensitive."
msgstr ""
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "English (provided by Drupal)"
msgstr "Англиски (од „Drupal“)"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "Search in"
msgstr "Барај во"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "All strings in that language"
msgstr "Сите стрингови во тој јазик"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "Only translated strings"
msgstr "Само преведени стрингови"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "Only untranslated strings"
msgstr "Само непреведени стрингови"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid "Search strings"
msgstr "Пребарувај стрингови"
#: /~linuxnetmk/?q=admin/locale/string/search
msgid ""
" It is often more convinient to get the strings of your setup on the "
"export page, and start with a desktop Gettext "
"translation editor though. Here you can search in the translated and "
"untranslated strings, and the default English texts provided by "
"Drupal. Blocks are the boxes visible in the sidebar(s) of your web site. "
"These are usually generated automatically by modules (e.g. recent "
"forum topics), but you can also create your own blocks. The sidebar each block appears in depends on both which theme "
"you're using (some are left-only, some right, some both), and on the "
"settings in block management. Whether a block is visible in the "
"first place depends on four things: The block management screen also lets you specify the vertical "
"sort-order of the blocks within a sidebar. You do this by assigning a "
"weight to each block. Lighter blocks (smaller weight) "
"\"float up\" towards the top of the sidebar. Heavier ones \"sink "
"down\" towards the bottom of it. The path setting lets you define the pages on which a specific "
"block is visible. If you leave the path blank it will appear on all "
"pages. The path uses a regular expression syntax so remember to escape "
"special characters! The path expression is matched against the "
"relative URL of a Drupal page, e.g. In case you do not know what a regular expression is, you should "
"read about them in the PHP manual. The chapter to look at is the one "
"on Perl-Compatible Regular Expressions "
"(PCRE). However, for basic tasks it is sufficient to look at the following "
"examples: If the block should only show up on blog pages, use <^blog>. "
"To display on all node views use <^node>. The angular brackets "
"are used as delimiters of the regular expression. To show up on "
"either forum or book pages use <^(forum|book)>. The round "
"brackets form a group of expressions, divided by the | character. It "
"matches if any of the expressions in it match. A more complicated "
"example is <^node/add/(story|blog|image)>. Blocks which have "
"their paths set to this expression will show up on story, block, or "
"image composition pages. If you want to show a block an all pages, "
"but not the search page, use <^(?!search)>. An administrator defined block contains content supplied by you (as "
"opposed to being generated automatically by a module). Each "
"admin-defined block consists of a title, a description, and a body "
"which can be as long as you wish. The Drupal engine will 'render' the "
"content of the block. If you know how to script in PHP, Drupal gives you the power to "
"embed any script you like. It will be executed when the page is viewed "
"and dynamically embedded into the page. This gives you amazing "
"flexibility and power, but of course with that comes danger and "
"insecurity if you don't write good code. If you are not familiar with "
"PHP, SQL or with the site engine, avoid experimenting with PHP because "
"you can corrupt your database or render your site insecure or even "
"unusable! If you don't plan to do fancy stuff with your content then "
"you're probably better off with straight HTML. Remember that the code within each PHP item must be valid PHP code "
"- including things like correctly terminating statements with a "
"semicolon. It is highly recommended that you develop your code "
"separately using a simple test script on top of a test database before "
"migrating to your production environment. Notes: A basic example: You want to have a box with the title \"Welcome\" that "
"you use to greet your visitors. The content for this box could be "
"created by going: If we are however dealing with a registered user, we can customize "
"the message by using: For more in-depth examples, we recommend that you check the "
"existing Drupal code and use it as a starting point, especially for "
"sidebar boxes. The search page allows you to search the web site's content. "
"You can specify multiple words, and they will all be searched for. "
"You can also use wildcards, so 'walk*' will match 'walk', 'walking', "
"'walker', 'walkable' and so on. Furthermore, searches are not case "
"sensitive so searching for 'walk', 'Walk' or 'WALK' will yield exactly "
"the same results. Words that frequently occur, typically called 'noise words', "
"are ignored. Example words are 'a', 'at', 'and', 'are', 'as', 'how', "
"'where', etc. Words shorter than %number letters are also "
"ignored. Страницата за пребарување ти "
"дозволува да ја пребараш содржината "
"на веб сајтот. Можеш да одредиш повеќе "
"зборови, и сите ќе бидат пребарани. "
"Исто така можеш да користиш и знаци, "
"така што „оди*“ ќе го пронајде „оди“, "
"„одење“, „одење*“ итн. Зборови кои што се појавуваат често, "
"односно т.н „гласни зборови“, се "
"игнорирани. Како на пример: „на“, "
"„во“, „и“, „се“, „како“, „“кога, "
"„каде“, итн. Зборови со помалку од "
"%number букви исто така ќе бидат "
"игнорирани. Taxonomy is the study of classification. Drupal's taxonomy "
"module allows you to define vocabularies which are used to classify "
"content. The module supports hierarchical classification and "
"association between terms, allowing for truly flexible information "
"retrieval and classification. For more details about classification types and insight "
"into the development of the taxonomy module, see this drupal.org discussion. Notes When you create a controlled vocabulary you are creating a "
"set of terms to use for describing content (known as descriptors in "
"indexing lingo). Drupal allows you to describe each piece of content "
"(blog, story, etc.) using one or many of these terms. For simple "
"implementations, you might create a set of categories without "
"subcategories, similar to Slashdot's "
"sections. For more complex implementations, you might create a "
"hierarchical list of categories such as Food taxonomy shown "
"above. When setting up a controlled vocabulary, if you select the "
"hierarchy option, you will be defining a tree structure of "
"terms, as in a thesaurus. If you select the related terms "
"option, you are allowing the definition of related terms (think "
"see also), as in a thesaurus. Selecting multiple "
"select will allow you to describe a piece of content using more "
"than one term. That content will then appear on each term's page, "
"increasing the chance that a user will find it. When setting up a controlled vocabulary you are asked for: "
"How to interface translation works
\n"
"
\n"
"book, "
"node/12, admin.Administrator Defined Blocks
\n"
"themes/phptemplate and copy the contents of an existing "
"template (e.g. themes/phptemplate/default) into it. The "
"new template will automatically become available in the selection menu "
"and will be identified by its directory name."
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Template selection"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Logo image"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Site links"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Avatars with posts"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Avatars with comments"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Path to logo"
msgstr "Патека до лого"
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"Path to logo to display instead of the template\" default logo.png "
"file"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Default avatar"
msgstr "Стандарден аватар"
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"Path to avatar to display for users with no custom avatar selected. "
"Default: None"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Navigation links"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"Enter a list of html links separated by semi-colons (;) to override "
"the default navigation links."
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Alternative front page message"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"This field can be used to customize the message on the front page (if "
"enabled). It can be used to display a mission statement, announcement "
"or site description."
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid "Engine-specific settings"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"These settings only exist for all the templates and styles based on "
"the %engine theme engine."
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate.marvin_2k
msgid ""
"These options control the display settings for the "
"%template theme. When your site is displayed using this "
"theme, these settings will be used. By clicking \"Reset to defaults,\" "
"you can choose to use the global settings for "
"this theme."
msgstr ""
#: /~linuxnetmk/?q=admin/block
msgid "the block settings have been updated."
msgstr ""
#: /~linuxnetmk/?q=filter/tips
msgid ""
"\n"
"Using custom PHP code
\n"
"
\n"
"print or return statement "
"to output the actual content for your item.
\n"
"\n"
" print t(\"Welcome visitor, ... welcome message goes here ...\");\n"
"
\n"
"\n"
" global $user;\n"
" if ($user->uid) {\n"
" print t(\"Welcome $user->name, ... welcome message goes here "
"...\");\n"
" }\n"
" else {\n"
" print t(\"Welcome visitor, ... welcome message goes here ...\");\n"
" }\n"
"ModRewrite support. See also the .htaccess "
"file in Drupal's top-level directory."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "1 hour"
msgstr "1 час"
#: /~linuxnetmk/?q=admin/settings
msgid "Never"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Default 403 (access denied) page"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"This page is displayed when the requested document is denied to the "
"current user. If you are not using clean URLs, specify the part after "
"\"?q=\". If unsure, specify nothing."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Default 404 (not found) page"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"This page is displayed when no other content matches the requested "
"document. If you are not using clean URLs, specify the part after "
"\"?q=\". If unsure, specify nothing."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Error reporting"
msgstr "Пријавување на грешки"
#: /~linuxnetmk/?q=admin/settings
msgid "Write errors to the log"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Write errors to the log and to the screen"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"Where Drupal, PHP and SQL errors are logged. On a production server it "
"is recommended that errors are only written to the error log. On a "
"test server it can be helpful to write logs to the screen."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Discard log entries older than"
msgstr "Избриши ги логовите постари од"
#: /~linuxnetmk/?q=admin/settings
msgid ""
"The time log entries should be kept. Older entries will be "
"automatically discarded. Requires crontab."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Error handling"
msgstr "Справување со грешки"
#: /~linuxnetmk/?q=admin/settings
msgid "Cache support"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"Enable or disable the caching of rendered pages. When caching is "
"enabled, Drupal will flush the cache when required to make sure "
"updates take effect immediately. Check the cache documentation for information on "
"Drupal's cache system."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Cache settings"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "File system path"
msgstr "Системска патека за датотеки"
#: /~linuxnetmk/?q=admin/settings
msgid ""
"A file system path where the files will be stored. This directory has "
"to exist and be writable by Drupal. If the download method is set to "
"public this directory has to be relative to Drupal installation "
"directory, and be accessible over the web. When download method is set "
"to private this directory should not be accessible over the web. "
"Changing this location after the site has been in use will cause "
"problems so only change this setting on an existing site if you know "
"what you are doing."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Temporary directory"
msgstr "Привремен директориум"
#: /~linuxnetmk/?q=admin/settings
msgid ""
"Location where uploaded files will be kept during previews. Relative "
"paths will be resolved relative to the file system path."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Download method"
msgstr "Метод на преземање"
#: /~linuxnetmk/?q=admin/settings
msgid "Public - files are available using http directly."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Private - files are transferred by Drupal."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"If you want any sort of access control on the downloading of files, "
"this needs to be set to private. You can change this at any "
"time, however all download URLs will change and there may be "
"unexpected problems so it is not recommended."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "File system settings"
msgstr "Подесувања за датотечниот систем"
#: /~linuxnetmk/?q=admin/settings
msgid "pm"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Sun"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Default time zone"
msgstr "Стандардна временска зона"
#: /~linuxnetmk/?q=admin/settings
msgid "Select the default site time zone."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Configurable time zones"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid ""
"Enable or disable user-configurable time zones. When enabled, users "
"can set their own time zone and dates will be updated accordingly."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Short date format"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "The short format of date display."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Medium date format"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "The medium sized date display."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Long date format"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Longer date format used for detailed display."
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "First day of week"
msgstr "Прв ден од неделата"
#: /~linuxnetmk/?q=admin/settings
msgid "The first day of the week for calendar views."
msgstr "Прв ден од неделата."
#: /~linuxnetmk/?q=admin/settings
msgid "Date settings"
msgstr "Подесувања за датумот"
#: /~linuxnetmk/?q=admin/settings
msgid ""
"General configuration options for your site. Set up the name of the "
"site, e-mail address used in mail-outs, clean URL options, caching, "
"etc."
msgstr ""
#: /~linuxnetmk/?q=admin/logs/hits/page/Open-Xchange%3A+%D0%BE%D1%81%D0%BB%D0%BE%D0%B1%D0%BE%D0%B4%D0%B5%D1%82%D0%B5+%D1%81%D0%B5+%
msgid "track user"
msgstr ""
#: /~linuxnetmk/?q=admin/logs/hits/page/Open-Xchange%3A+%D0%BE%D1%81%D0%BB%D0%BE%D0%B1%D0%BE%D0%B4%D0%B5%D1%82%D0%B5+%D1%81%D0%B5+%
msgid "track title"
msgstr ""
#: /~linuxnetmk/?q=admin/logs/hits/page/Open-Xchange%3A+%D0%BE%D1%81%D0%BB%D0%BE%D0%B1%D0%BE%D0%B4%D0%B5%D1%82%D0%B5+%D1%81%D0%B5+%
msgid "track host"
msgstr ""
#: /~linuxnetmk/?q=search
msgid "Restrict search to"
msgstr "Ограничи го пребарувањето на"
#: /~linuxnetmk/?q=search
msgid ""
"\n"
" Search guidelines\n"
" Background
\n"
" An example taxonomy: food
\n"
" "
"
\n"
"
\n"
" Vocabularies
\n"
" Setting up a vocabulary
\n"
" \n"
"
Once done defining the vocabulary, you have to add terms to " "it to make it useful. The options you see when adding a term to a " "vocabulary will depend on what you selected for related " "terms, hierarchy and multiple select. These " "options are:
\n" "In order to view the content associated with a term or a " "collection of terms, you should browse to a properly formed Taxonomy " "URL. For example, taxonomy/term/1+2. " "Taxonomy URLs always contain one or more term IDs at the end of the " "URL. You may learn the term ID for a given term by hovering over that " "term in the taxonomy overview page and " "noting the number at the end or the URL. To build a Taxonomy URL " "start with \"taxonomy/term/\". Then list the term IDs, separated by " "\"+\" to choose content tagged with any of the given " "term IDs, or separated by \",\" to choose content tagged with " "all of the given term IDs. In other words, \"+\" is " "less specific than \",\". Finally, you may optionally specify a " "\"depth\" in the vocabulary hierarchy. This defaults to \"0\", which " "means only the explicitly listed terms are searched. A positive number " "indicates the number of additional levels of the tree to search. You " "may also use the value \"all\", which means that all descendant terms " "are searched.
\n" "Every term, or collection of terms, provides an RSS feed to which interested users may " "subscribe. The URL format for a sample RSS feed is taxonomy/term/1+2/0/feed. These are built " "just like Taxonomy URLs, but are followed " "by the word \"feed\".
" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "Term name" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "The name for this term. Example: \"Linux\"." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "A description of the term." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "Parent" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "Parent term" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "root" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "Synonyms" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "Synonyms of this term, one synonym per line." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/term/28 msgid "" "In listings, the heavier terms will sink and the lighter terms will be " "positioned nearer the top." msgstr "" #: /~linuxnetmk/?q=admin/node msgid "View posts that are new or updated" msgstr "Види нови или ажурирани вести" #: /~linuxnetmk/?q=admin/node msgid "View posts that need approval" msgstr "Види вести на кои им треба дозвола" #: /~linuxnetmk/?q=admin/node msgid "View posts that are promoted" msgstr "Види унапредени вести" #: /~linuxnetmk/?q=admin/node msgid "View posts that are not promoted" msgstr "Види вести кои не се унапредени" #: /~linuxnetmk/?q=admin/node msgid "View posts that are sticky" msgstr "Види лепливи вести" #: /~linuxnetmk/?q=admin/node msgid "View posts that are unpublished" msgstr "Види вести кои не се објавени" #: /~linuxnetmk/?q=admin/node msgid "Approve the selected posts" msgstr "Одобри ги избраните вести" #: /~linuxnetmk/?q=admin/node msgid "Promote the selected posts" msgstr "" #: /~linuxnetmk/?q=admin/node msgid "Make the selected posts sticky" msgstr "" #: /~linuxnetmk/?q=admin/node msgid "Demote the selected posts" msgstr "" #: /~linuxnetmk/?q=admin/node msgid "Unpublish the selected posts" msgstr "" #: /~linuxnetmk/?q=admin/node msgid "Filter" msgstr "Филтер" #: /~linuxnetmk/?q=admin/node msgid "Update" msgstr "Ажурирај" #: /~linuxnetmk/?q=admin/node msgid "Filter options" msgstr "Опции за филтри" #: /~linuxnetmk/?q=admin/node msgid "Update options" msgstr "Ажурирај опции" #: /~linuxnetmk/?q=admin/node msgid "Title" msgstr "Наслов" #: /~linuxnetmk/?q=admin/node msgid "published" msgstr "објавено" #: /~linuxnetmk/?q=admin/node msgid "" "Below is a list of all of the posts on your site. Other forms of " "content are listed elsewhere (e.g. comments).The core of the Drupal system is the node. All of the " "contents of the system are placed in nodes, or extensions of nodes.\n" " A base node contains:
Now that you know what is in a node, here are some of the " "types of nodes available.
" msgstr "" #: /~linuxnetmk/?q=admin/node msgid "Node type: %module" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Vocabulary name" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "The name for this vocabulary. Example: \"Topic\"." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Description of the vocabulary; can be used by modules." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Help text" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Instructions to present to the user when choosing a term." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Types" msgstr "Типови" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "A list of node types you want to associate with this vocabulary." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Related terms" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Allows related terms in this vocabulary." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Hierarchy" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Single" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Multiple" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "" "Allows a tree-like hierarchy between terms " "of this vocabulary." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Multiple select" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Allows nodes to have more than one term in this vocabulary." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "Required" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "" "If enabled, every node must have at least one term in " "this vocabulary." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/edit/vocabulary/1 msgid "" "In listings, the heavier vocabularies will sink and the lighter " "vocabularies will be positioned nearer the top." msgstr "" #: /~linuxnetmk/?q=admin/filters msgid "Save input formats" msgstr "Зачувај ги влезните формати" #: /~linuxnetmk/?q=admin/filters msgid "Add input format" msgstr "" #: /~linuxnetmk/?q=admin/filters msgid "Permissions and settings" msgstr "" #: /~linuxnetmk/?q=admin/filters msgid "" "To add a new input format, type its name here. After it has been " "added, you can configure its options.
" msgstr "" #: /~linuxnetmk/?q=admin/filters msgid "Add new input format" msgstr "" #: /~linuxnetmk/?q=admin/filters msgid "" "\n" "Input formats define a way of processing user-supplied " "text in Drupal. Every input format has its own settings of which " "filters to apply. Possible filters include stripping out " "malicious HTML and making URLs clickable.
\n" "Users can choose between the available input formats when " "submitting content.
\n" "Below you can configure which input formats are available to which " "roles, as well as choose a default input format (used for imported " "content, for example).
" msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "Choice %n" msgstr "Избор %n" #: /~linuxnetmk/?q=node/1031/edit msgid "Need more choices" msgstr "Ми требаат повеќе избори" #: /~linuxnetmk/?q=node/1031/edit msgid "" "If the amount of boxes above isn't enough, check this box and click " "the Preview button below to add some more." msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "Choices" msgstr "Избори" #: /~linuxnetmk/?q=node/1031/edit msgid "Unlimited" msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "1 year" msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "Closed" msgstr "Затворена" #: /~linuxnetmk/?q=node/1031/edit msgid "When a poll is closed, visitors can no longer vote for it." msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "After this period, the poll will be closed automatically." msgstr "" #: /~linuxnetmk/?q=node/1031/edit msgid "Settings" msgstr "Подесувања" #: /~linuxnetmk/?q=node/1031/edit msgid "Authored on" msgstr "Пратено на" #: /~linuxnetmk/?q=node/1031/edit msgid "Authoring information" msgstr "Информации за испраќачот" #: /~linuxnetmk/?q=node/1031/edit msgid "Published" msgstr "Објавено" #: /~linuxnetmk/?q=node/1031/edit msgid "In moderation queue" msgstr "Во листа на чекање" #: /~linuxnetmk/?q=node/1031/edit msgid "Promoted to front page" msgstr "Да се појави на предната страница" #: /~linuxnetmk/?q=node/1031/edit msgid "Sticky at top of lists" msgstr "Лепливите најгоре" #: /~linuxnetmk/?q=node/1031/edit msgid "Create new revision" msgstr "Нова ревизија" #: /~linuxnetmk/?q=node/1031/edit msgid "Options" msgstr "Опции" #: /~linuxnetmk/?q=node/1031/edit msgid "Read only" msgstr "Само за читање" #: /~linuxnetmk/?q=node/1031/edit msgid "Read/write" msgstr "Читање и запишување" #: /~linuxnetmk/?q=admin/logs/view/301 msgid "Location" msgstr "Локација" #: /~linuxnetmk/?q=admin/comment msgid "Subject" msgstr "Тема" #: /~linuxnetmk/?q=admin/comment msgid "Time" msgstr "Време" #: /~linuxnetmk/?q=admin/comment msgid "Aug" msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "Jul" msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "Jun" msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "Apr" msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "Mar" msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "" "Below is a list of the latest comments posted your site. Click on a " "subject to see the comment, the author's name to edit the author's " "user information , \"edit\" to modify the text, and \"delete\" to " "remove their submission." msgstr "" #: /~linuxnetmk/?q=admin/comment msgid "" "\n" "When enabled, the Drupal comment module creates a discussion " "board for each Drupal node. Users can post comments to discuss a forum " "topic, weblog post, story, collaborative book page, etc. An " "administrator can give comment permissions to user groups, and users " "can (optionally) edit their last comment, assuming no others have been " "posted since.
\n" "\n" "Attached to each comment board is a control panel for " "customizing the way that comments are displayed. Users can control the " "chronological ordering of posts (newest or oldest first) and the " "number of posts to display on each page. Additional settings " "include:
\n" "When a user chooses save settings, the comments are " "then redisplayed using the user's new choices. Administrators can set " "the default settings for the comment control panel, along with other " "comment defaults, in administer » " "comments » configure. NOTE: When comment moderation is " "enabled, users will have another control panel option to control " "thresholds (see below).
\n" "\n" "Comments behave like other user submissions in Drupal. " "Filters, smileys and HTML that work in nodes will also work with " "comments. Administrators can control access to various comment module " "functions through administer » " "users » configure » permissions. Know that in a new " "Drupal installation, all comment permissions are disabled by default. " "The choice of which permissions to grant to which roles (groups of " "users) is left up to the site administrator. The following " "permissions:
\n" "Drupal provides specific features to inform site members when " "new comments have been posted.
\n" "Drupal displays the total number of comments attached to each " "node, and tracks comments read by individual site members. Members " "which have logged in will see a notice accompanying nodes which " "contain comments they have not read. Some administrators may want to " "download, install and configure the " "notify module. Users can then request that Drupal send them an " "e-mail when new comments are posted (the notify module requires that " "cron.php be configured properly).
\n" "The tracker module, disabled by default, displays " "all the site's recent posts. There is a link to the recent posts page in the navigation block. This " "page is a useful way to browse new or updated nodes and comments. " "Content which the user has not yet read is tagged with a red star " "(this graphic depends on the current theme). Visit the comment board " "for any node, and Drupal will display a red \"new\" label " "beside the text of unread comments.
\n" "\n" "On sites with active commenting from users, the administrator " "can turn over comment moderation to the community.
\n" "With comment moderation, each comment is automatically " "assigned an initial rating. As users read comments, they can apply a " "vote which affects the comment rating. At the same time, users have an " "additional option in the control panel which allows them to set a " "threshold for the comments they wish to view. Those comments with " "ratings lower than the set threshold will not be shown. To enable " "moderation, the administrator must grant moderate comments permissions. Then, a " "number of options in administer » " "comments » configure must be configured.
\n" "\n" "The first step is to create moderation labels which allow " "users to rate a comment. Go to administer " "» comments » configure » moderation votes. In " "the vote field, enter the textual labels which users will see " "when casting their votes. Some examples are
\n" "So that users know how their votes affect the comment, these " "examples include the vote value as part of the label, although that is " "optional. Using the weight option, you can control the order in which " "the votes appear to users. Setting the weight heavier (positive " "numbers) will make the vote label appear at the bottom of the list. " "Lighter (a negative number) will push it to the top. To encourage " "positive voting, a useful order might be higher values, positive " "votes, at the top, with negative votes at the bottom.
\n" "\n" "Next go to administer » " "comments » configure » moderation matrix. Enter the " "values for the vote labels for each permission role in the vote " "matrix. The values entered here will be used to create the rating for " "each comment. NOTE: Comment ratings are calculated by averaging user " "votes with the initial rating.
\n" "\n" "In administer » " "comments » configure » moderation thresholds, you'll " "have to create some comment thresholds to make the comment rating " "system useful. When comment moderation is enabled and the thresholds " "are created, users will find another comment control panel option for " "selecting their thresholds. They'll use the thresholds you enter here " "to filter out comments with low ratings. Consequently, you'll probably " "want to create more than one threshold to give users some flexibility " "in filtering comments.
\n" "When creating the thresholds, note that the Minimum " "score is asking you for the lowest rating that a comment can have " "in order to be displayed. To see a common example of how thresholds " "work, you might visit Slashdot and view one " "of their comment boards associated with a story. You can reset the " "thresholds in their comment control panel.
\n" "\n" "Finally, you may want to enter some initial comment " "scores. In administer » " "comments » configure » moderation roles you can assign " "a beginning rating for all comments posted by a particular permission " "role. If you do not assign any initial scores, Drupal will assign a " "rating of 0 as the default.
" msgstr "" #: /~linuxnetmk/?q=admin/user msgid "Create account" msgstr "" #: /~linuxnetmk/?q=admin/user msgid "ID" msgstr "" #: /~linuxnetmk/?q=admin/user msgid "Last access" msgstr "Последен пат пристапено" #: /~linuxnetmk/?q=admin/user msgid "operations" msgstr "операции" #: /~linuxnetmk/?q=admin/user msgid "blocked" msgstr "блокирано" #: /~linuxnetmk/?q=admin/user msgid "active" msgstr "активен" #: /~linuxnetmk/?q=admin/user msgid "" "Drupal allows users to register, login, logout, maintain user " "profiles, etc. No participant can use his own name to post content " "until he signs up for a user account." msgstr "" #: /~linuxnetmk/?q=admin/user msgid "" "\n" "Drupal offers a powerful access system that allows users to " "register, login, logout, maintain user profiles, etc. By using roles you can setup fine grained permissions allowing each role to do " "only what you want them to. Each user is assigned to one or more " "roles. By default there are two roles \"anonymous\" - a user who has " "not logged in, and \"authorized\" a user who has signed up and who has " "been authorized. As anonymous users, participants suffer numerous " "disadvantages, for example they cannot sign their names to nodes, and " "their moderated posts beginning at a lower score.
\n" "In contrast, those with a user account can use their own name " "or handle and are granted various privileges: the most important is " "probably the ability to moderate new submissions, to rate comments, " "and to fine-tune the site to their personal liking, with saved " "personal settings. Drupal themes make fine tuning quite a " "pleasure.
\n" "Registered users need to authenticate by supplying either a " "local username and password, or a remote username and password such as " "a Jabber ID, DelphiForums ID, or one from a Drupal powered website. See the distributed authentication help for more " "information on this innovative feature.\n" " The local username and password, hashed with Message Digest 5 " "(MD5), are stored in your database. When you enter a password it is " "also hashed with MD5 and compared with what is in the database. If the " "hashes match, the username and password are correct. Once a user " "authenticated session is started, and until that session is over, the " "user won't have to re-authenticate. To keep track of the individual " "sessions, Drupal relies on PHP sessions. A " "visitor accessing your website is assigned an unique ID, the so-called " "session ID, which is stored in a cookie. For security's sake, the " "cookie does not contain personal information but acts as a key to " "retrieve the information stored on your server. When a visitor " "accesses your site, Drupal will check whether a specific session ID " "has been sent with the request. If this is the case, the prior saved " "environment is recreated.
\n" "Each Drupal user has a " "profile, and a set of preferences which may be edited by clicking on " "the \"my account\" link. Of course, a user " "must be logged into reach those pages. There, users will find a page " "for changing their preferred time zone, language, username, e-mail " "address, password, theme, signature, and distributed authentication names. Changes made " "here take effect immediately. Also, administrators may make profile " "and preferences changes in account " "administration on behalf of their users.
\n" "\n" "One of the more tedious moments in visiting a new website is " "filling out the registration form. The reg form provides helpful " "information to the website owner, but not much value for the user. The " "value for the end user is usually the ability to post a messages or " "receive personalized news, etc. Distributed authentication (DA) gives " "the user what they want without having to fill out the reg form. " "Removing this obstacle yields more registered and active users for the " "website.
\n" "DA enables a new user to input a username and password into " "the login box and immediately be recognized, even if that user never " "registered on your site. This works because Drupal knows how to " "communicate with external registration databases. For example, lets " "say that your new user 'Joe' is already a registered member of Delphi " "Forums. If your Drupal has the delphi module installed, then Drupal " "will inform Joe on the registration and login screens that he may " "login with his Delphi ID instead of registering with your Drupal " "instance. Joe likes that idea, and logs in with a username of " "joe@remote.delphiforums.com and his usual Delphi password. Drupal then " "communicates with remote.delphiforums.com (usually using XML, HTTP-POST, or SOAP) behind the scenes and asks "is this " "password for username=joe?" If Delphi replies yes, then Drupal " "will create a new local account for joe and log joe into it. Joe may " "keep on logging into your Drupal instance in the same manner, and he " "will be logged into the same joe@remote.delphiforums.com " "account.
\n" "One key element of DA is the 'authmap' table, which maps a " "user's authname (e.g. joe@remote.delphiforums.com) to his local UID " "(i.e. user identification number). This map is checked whenever a user " "successfully logs into an external authentication source. Once Drupal " "knows that the current user is definitely joe@remote.delphiforums.com " "(because Delphi says so), he looks up Joe's UID and logs Joe into that " "account.
\n" "To disable distributed authentication, simply disable or remove all DA modules. For a " "virgin install, that means removing/disabling the jabber module and " "the drupal module.
\n" "Drupal is setup so that it is very easy to add support for " "any external authentication source. You currently have the following " "authentication modules installed ...
" msgstr "" #: /~linuxnetmk/?q=admin/taxonomy/image msgid "name" msgstr "име" #: /~linuxnetmk/?q=admin/taxonomy/image msgid "node types" msgstr "тип на содржина" #: /~linuxnetmk/?q=admin/taxonomy/image msgid "image" msgstr "слика" #: /~linuxnetmk/?q=admin/taxonomy/image msgid "upload image" msgstr "подигни слика" #: /~linuxnetmk/?q=admin/taxonomy/image msgid "" "The taxonomy_image module allows site administrators to associate " "images with taxonomy terms. Once defined, this association allows " "Drupal themes to display images with site content. For example, this " "module might be used to display a penguin with content about Linux, " "and a cheeseburger with content about junk food. To upload a new " "image for a specific term, click \"upload image\" next to the term. " "To modify or delete and existing image, click \"edit image\". To " "learn more about how to create vocabularies and terms, review the taxonomy help page." msgstr "" #: /~linuxnetmk/?q=admin/taxonomy_image msgid "" "\n" "The taxonomy_image module allows site administrators to " "associate images with taxonomy terms. Once defined, this association " "allows Drupal themes to display images with site content. For " "example, the taxonomy_image module might be used to display a penguin " "with content about Linux, and a cheeseburger with content about junk " "food.
\n" "The module allows both a one-to-one term-to-image " "relationship, and a many-to-one terms-to-image relationship.
\n" "The taxonomy_image module requires that the taxonomy module " "also be enabled.
\n" "With the taxonomy_image module enabled, images can be " "uploaded and associated with taxonomy terms at 'administer >> " "categories >> images'. On that page you will find tables containing " "all your vocabularies and terms. Next to each term is a link titled " "'upload image' which you can click to upload an image for that term. " "After clicking that link, you will be brought to another page with a " "small 'Add images' form. Using the 'browse' button you can select " "your image then click 'Save'.\n" "
Continue this process to upload appropriate images for your " "taxonomy terms. Note that by default images will be displayed at the " "size they were uploaded. Alternatively, you can go to 'administer >> " "settings >> taxonomy_image' to force the display height and/or width " "of all taxonomy images.
\n" "For your users to be able to view the images you have " "uploaded, you will need to give them the necessary permissions. Only " "users with the 'access taxonomy images' permission will see images. " "If you wish to give your users the ability to disable the images, also " "give them the 'can disable taxonomy images' permission.
\n" "A third permission, 'administer taxonomy images', controls " "which users are allowed to configure taxonomy images.
\n" "Taxonomy is a very powerful tool. One of its features is " "providing the ability to create hierarchical vocabularies, with which " "you can build a tree of terms. It is possible that an entire tree of " "terms, or even just a branch of terms, are all about a similar subject " "and should all be associated with the same image. By going to " "'administer >> settings >> taxonomy_image', you can enable 'Recursive " "image disaply'. With this option enabled, you only need to configure " "an image for the parent term, and all children will automatically " "inheret the same image (unless they are manually configured to display " "an alternative image).
\n" "To actually display images from your theme, you will have to " "modify the theme to make a call to taxonomy_image_display(). When " "calling this function, you will need to pass in the taxonomy term for " "which an image should be displayed. For example, from your theme's " "'_node' function you might do the following:\n" "
\n"
" foreach (taxonomy_node_get_terms($node->nid) as $term) {\n"
" if ($image = taxonomy_image_display($term->tid)) {\n"
" $output .= \"$image\";\n"
" }\n"
"\n"
msgstr ""
#: /~linuxnetmk/?q=admin/taxonomy/image/add/2
msgid "Taxonomy image file"
msgstr ""
#: /~linuxnetmk/?q=admin/taxonomy/image/add/2
msgid "The image file you wish to associate with the '%term' term."
msgstr ""
#: /~linuxnetmk/?q=admin/taxonomy/image/add/2
msgid "Upload new image"
msgstr "Подигни нова слика"
#: /~linuxnetmk/?q=admin/taxonomy/image/add/28
msgid "%error: %message in %file on line %line."
msgstr ""
#: /~linuxnetmk/?q=admin/taxonomy/image/add/28
msgid "Image uploaded."
msgstr "Сликата е подигната."
#: /~linuxnetmk/?q=admin/taxonomy/image/add/28
msgid "edit image"
msgstr "уреди слика"
#: /~linuxnetmk/?q=admin/taxonomy/image/edit/53
msgid "Current image"
msgstr "Тековна слика"
#: /~linuxnetmk/?q=admin/taxonomy/image/edit/53
msgid "Edit image"
msgstr "Уреди слика"
#: /~linuxnetmk/?q=admin/taxonomy/image/edit/53
msgid "Image deleted."
msgstr "Сликата е избришана."
#: /~linuxnetmk/?q=poll/vote/1048
msgid "Your vote was recorded."
msgstr "Твојот глас е регистриран."
#: /~linuxnetmk/?q=node/1048
msgid "%count votes"
msgstr "гласови"
#: /~linuxnetmk/?q=poll
msgid "open"
msgstr ""
#: /~linuxnetmk/?q=admingdsf
msgid "404 error: %page not found."
msgstr ""
#: /~linuxnetmk/?q=admingdsf
msgid "Page not found"
msgstr "Страната не е најдена"
#: /~linuxnetmk/?q=node/5/edit
msgid "Body"
msgstr "Текст"
#: /~linuxnetmk/?q=node/5/edit
msgid "%type: updated %title."
msgstr ""
#: /~linuxnetmk/?q=node/5/edit
msgid "The %post was updated."
msgstr "%post е ажурирана."
#: /~linuxnetmk/?q=admin/settings
msgid "am"
msgstr ""
#: /~linuxnetmk/?q=admin/settings
msgid "Wed"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "Add rule"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "Check"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "Permission"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "%module module"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access news feeds"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer news feeds"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer blocks"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access comments"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer comments"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer moderation"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "post comments"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "post comments without approval"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer filters"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer locales"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access content"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer nodes"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "create pages"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "edit own pages"
msgstr "уреди ги твоите страници"
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "create polls"
msgstr "креирај анкети"
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "vote on polls"
msgstr "гласај на анкети"
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer search"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "search content"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access statistics"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer statistics"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer statistics module"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "create stories"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "edit own stories"
msgstr "уреди ги твоите стории"
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access administration pages"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer site configuration"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "bypass input data check"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer taxonomy"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "access taxonomy images"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer taxonomy images"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "can disable taxonomy images"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer users"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "administer watchdog"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid ""
"In this area you will define the permissions for each user role (role "
"names are defined on the user roles page). Each "
"permission describes a fine-grained logical operation, such as being "
"able to access the administration pages, or adding/modifying a user "
"account. You could say a permission represents access granted to a "
"user to perform a set of operations."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/permission
msgid "The user permissions have been saved."
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate
msgid "Taxonomy images"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate
msgid "Theme-specific settings"
msgstr ""
#: /~linuxnetmk/?q=admin/themes/settings/phptemplate
msgid ""
"These settings only exist for the %theme theme and all the styles "
"based on it."
msgstr ""
#: /~linuxnetmk/?q=admin/block/add
msgid ""
"Here you can create a new block. Once you have created this block you "
"must make it active and give it a place on the page using blocks. The title is used when displaying the "
"block. The description is used in the \"block\" column on the blocks page."
msgstr ""
"Овде можеш да креираш нов блок. Откако "
"ќе го креираш блокот мораш да го "
"активираш и да му одредиш место на "
"страницата со користење на блокови. Насловот се "
"користи при прикажување на блокот. "
"Описот се користи во колоната „блок“ "
"на страницата блокови."
#: /~linuxnetmk/?q=admin/block/add
msgid "The new block has been added."
msgstr "Новиот блок е додаден."
#: /~linuxnetmk/?q=user/2002
msgid "The content of this field is private and only visible to yourself."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Add role"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Delete role"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Save role"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Public registrations"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Visitors can create accounts and no administrator approval is "
"required."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Visitors can create accounts but administrator approval is required."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"This text is displayed at the top of the user registration form. It's "
"useful for helping or instructing your users."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Subject of welcome e-mail"
msgstr "Тема на пораката за добродојде"
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Customize the subject of your welcome e-mail, which is sent to new "
"members upon registering."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Available variables are:"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Body of welcome e-mail"
msgstr "Текст на пораката за добродојде"
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Customize the body of the welcome e-mail, which is sent to new members "
"upon registering."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Subject of welcome e-mail (awaiting admin approval)"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Customize the subject of your awaiting approval welcome e-mail, which "
"is sent to new members upon registering."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Body of welcome e-mail (awaiting admin approval)"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Customize the body of the awaiting approval welcome e-mail, which is "
"sent to new members upon registering."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Subject of password recovery e-mail"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Customize the Subject of your forgotten password e-mail."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Body of password recovery e-mail"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Customize the body of the forgotten password e-mail."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Created directory %directory."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Picture support"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Enable picture support."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Subdirectory in the directory \"%dir\" where pictures will be stored."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Default picture"
msgstr "Стандардна слика"
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"URL of picture to display for users with no custom picture selected. "
"Leave blank for none."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Picture maximum dimensions"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Maximum dimensions for pictures."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Picture maximum file size"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Maximum file size for pictures, in kB."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "Picture guidelines"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"This text is displayed at the picture upload form in addition to the "
"default guidelines. It's useful for helping or instructing your "
"users."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid "%count sec"
msgstr "%count секунди"
#: /~linuxnetmk/?q=admin/user/configure
msgid "1 min"
msgstr "1 минута"
#: /~linuxnetmk/?q=admin/user/configure
msgid "%count min"
msgstr "%count минути"
#: /~linuxnetmk/?q=admin/user/configure
msgid "User list length"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"Affects \"Who's online\" block. Maximum number of currently online "
"users to display."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure
msgid ""
"In order to use the full power of Drupal a visitor must sign up for an "
"account. This page lets you setup how a user signs up, logs out, the "
"guidelines from the system about user subscriptions, and the e-mails "
"the system will send to the user."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "single-line textfield"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "multi-line textfield"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "checkbox"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "list selection"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "freeform list"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "URL"
msgstr "Адреса"
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "date"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "Category"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile
msgid "Add new field"
msgstr "Додади ново поле"
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"The category the new field should be part of. Categories are used to "
"group fields logically. An example category is \"Personal "
"information\"."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"The title of the new field. The title will be shown to the user. An "
"example title is \"Favorite color\"."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Form name"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"The name of the field. The form name is not shown to the user but "
"used internally in the HTML code and URLs.\n"
"Unless you know what you are doing, it is highly recommended that you "
"prefix the form name with profile_ to avoid name clashes "
"with other fields. Spaces or any other special characters except dash "
"(-) and underscore (_) are not allowed. An example name is "
"\"profile_favorite_color\" or perhaps just \"profile_color\"."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Explanation"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"An optional explanation to go with the new field. The explanation "
"will be shown to the user."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"The weights define the order in which the form fields are shown. "
"Lighter fields \"float up\" towards the top of the category."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Visibility"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Private field, content only available to privileged users."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"Public field, content shown on profile page but not used on member "
"list pages."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Public field, content shown on profile page and on member list pages."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Page title"
msgstr "Наслов на страна"
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid ""
"The title of the page showing all users with the specified field. "
"Only applicable if the field is configured to be shown on member "
"listings."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "The user must enter a value."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Visible in user registration form."
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Field settings"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Save field"
msgstr ""
#: /~linuxnetmk/?q=admin/user/configure/profile/edit/2
msgid "Edit %type"
msgstr ""
#: /~linuxnetmk/?q=user/register
msgid "New user: %name %email."
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid ""
"The content of this field is kept private and will not be shown "
"publicly."
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid "Jan"
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid "Feb"
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid "Sep"
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid "Nov"
msgstr ""
#: /~linuxnetmk/?q=user/2003/edit/Personal%20information
msgid "Dec"
msgstr ""
#: /~linuxnetmk/?q=node/997/edit
msgid "Preview trimmed version"
msgstr "Краток преглед"
#: /~linuxnetmk/?q=node/997/edit
msgid ""
"The trimmed version of your post shows what your post looks like when "
"promoted to the main page or when exported for syndication. You can "
"insert the delimiter \"<!--break-->\" (without the quotes) to "
"fine-tune where your post gets split."
msgstr ""
#: /~linuxnetmk/?q=node/997/edit
msgid "Preview full version"
msgstr "Целосен преглед"
#: /~linuxnetmk/?q=node/997/edit
msgid "Submit %name"
msgstr "Испрати %name"
#: /~linuxnetmk/?q=admin/aggregator
msgid "Feed overview"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid "Items"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid "Last update"
msgstr "Последно ажурирање"
#: /~linuxnetmk/?q=admin/aggregator
msgid "Next update"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid "%count items"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid "0 sec"
msgstr "0 секунди"
#: /~linuxnetmk/?q=admin/aggregator
msgid "%time left"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid "Category overview"
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid ""
"Thousands of sites (particularly news sites and weblogs) publish their "
"latest headlines and/or stories in a machine-readable format so that "
"other sites can easily link to them. This content is usually in the "
"form of an RSS "
"feed (which is an XML-based syndication standard). To display the feed "
"or category in a block you must decide how many items to show by "
"editing the feed or block and turning on the feed's "
"block."
msgstr ""
#: /~linuxnetmk/?q=admin/aggregator
msgid ""
"\n"
" Thousands of sites (particularly news sites and weblogs) " "publish their latest headlines and/or stories in a machine-readable " "format so that other sites can easily link to them. This content is " "usually in the form of an RSS feed (which is " "an XML-based syndication standard).
\n" "You can read aggregated content from many sites using RSS " "feed readers, such as Amphetadesk.
\n" "Drupal provides the means to aggregate feeds from many sites " "and display these aggregated feeds to your site's visitors. To do " "this, enable the aggregator module in site administration and then go " "to the aggregator configuration page, where you can subscribe to feeds " "and set up other options.
\n" "Many web sites (especially weblogs) display small XML icons " "or other obvious links on their home page. You can follow these to " "obtain the web address for the RSS feed. Common extensions for RSS " "feeds are .rss, .xml and .rdf. For example: Slashdot RSS.
\n" "If you can't find a feed for a site, or you want to find " "several feeds on a given topic, try an RSS syndication directory such " "as Syndic8.
\n" "To learn more about RSS, read Mark Pilgrim's What " "is RSS and WebReference.com's The " "Evolution of RSS articles.
\n" "NOTE: Enable your site's XML syndication button by turning on " "the Syndicate block in block management.
\n" "To subscribe to an RSS feed on another site, use the aggregation page.
\n" "Once there, click the new feed tab. " " Drupal will then ask for the following:
\n" "Once you have submitted the new feed, check to make sure it " "is working properly by selecting update " "items on the aggregation page. If you " "do not see any items listed for that feed, edit the feed and make sure " "that the URL was entered correctly.
\n" "News items can be filed into categories. To create a " "category, start at the aggregation " "page.
\n" "Once there, select new category " "from the menu. Drupal will then ask for the following:
\n" "The news aggregator has a number of ways that it displays " "your subscribed content:
\n" "Pages that display items (for sources, categories, etc.) " "display the following for each item:\n" "
Additionally, users with the administer news feeds " "permission will see a link to categorize the news items. Clicking " "this will allow them to select which category(s) each news item is " "in.
\n" "Drupal automatically generates an OPML feed file that is " "available by selecting the XML icon on the News Sources page.
\n" "When fetching feeds Drupal supports conditional GETs, this " "reduces the bandwidth usage for feeds that have not been updated since " "the last check.
\n" "If a feed is permanently moved to a new location Drupal will " "automatically update the feed URL to the new address.
" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "no block" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "3 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "5 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "10 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "15 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "20 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "25 items" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "" "The name of the feed; typically the name of the web site you syndicate " "content from." msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "The fully-qualified URL of the feed." msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "Update interval" msgstr "Ажурирај интервал" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "" "The refresh interval indicating how often you want to update this " "feed. Requires crontab." msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "Latest items block" msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "" "If enabled, a block containing the latest items from this feed will be " "available for placement on the block " "configuration page." msgstr "" #: /~linuxnetmk/?q=aggregator/sources/1/configure msgid "The feed has been updated." msgstr "" #: /~linuxnetmk/?q=admin/block msgid "%title feed latest items" msgstr "" #: /~linuxnetmk/?q=admin/block msgid "more" msgstr "повеќе" #: /~linuxnetmk/?q=admin/block msgid "View this feed's recent news." msgstr "" #: /~linuxnetmk/?q=aggregator/sources msgid "%age old" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "none" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "Items shown in sources and categories pages" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "" "The number of items which will be shown with each feed or category in " "the feed and category summary pages." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "Category selection type" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "checkboxes" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "multiple selector" msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "" "The type of category selection widget which is shown on categorization " "pages. Checkboxes are easier to use; a multiple selector is good for " "working with large numbers of categories." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/configure msgid "These settings control the display of aggregated content." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/update/1 msgid "Aggregator: failed to parse RSS feed %site: %error at line %line." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/update/1 msgid "Failed to parse RSS feed %site: %error at line %line." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/update/1 msgid "Aggregator: syndicated content from %site." msgstr "" #: /~linuxnetmk/?q=admin/aggregator/update/1 msgid "Syndicated content from %site." msgstr "" #: /~linuxnetmk/?q=admin/aggregator msgid "1 sec" msgstr "1 секунда" #: /~linuxnetmk/?q=admin/settings msgid "Thu" msgstr "" #: /cron.php msgid "Cron run completed" msgstr "" #: /node/add/page msgid "Formatting guidelines" msgstr "Правила за форматирање" #: /node/add/story msgid "%type: added %title." msgstr "" #: /node/add/story msgid "Your %post was created." msgstr "Твојата %post е креирана." #: /admin/taxonomy/edit/term/30 msgid "The term %term has been updated." msgstr "" #: /search msgid "Search: %keys." msgstr "Пребарувај: %keys." #: /search msgid "Matching comments ranked in order of relevance" msgstr "" "Пронајдените коментари прикажани по " "нивната важност" #: /search msgid "Matching nodes ranked in order of relevance" msgstr "" "Пронајдените точки прикажани по " "нивната важност" #: /search msgid "Matching users" msgstr "" #: /search msgid "Search Results" msgstr "Резултати од пребарувањето" #: /search msgid "Your search yielded no results." msgstr "" "Твоето пребарување не пронајде " "никакви резултати." #: /comment/reply/1048 msgid "Post comment" msgstr "Испрати коментар" #: /comment/reply/1048 msgid "Preview comment" msgstr "Прегледај коментар" #: /comment/reply/1048 msgid "Reply" msgstr "Реплика" #: /comment/reply/1048 msgid "Your name" msgstr "Твоето име" #: /comment/reply/1048 msgid "Comment" msgstr "Коментар" #: /comment/reply/1048 msgid "Add new comment" msgstr "Додај нов коментар" #: /admin/locale/language/export msgid "Export" msgstr "" #: /admin/locale/language/export msgid "Macedonian" msgstr "Македонски" #: /admin/locale/language/export msgid "English" msgstr "Англиски" #: /admin/locale/language/export msgid "Export translation" msgstr "" #: /admin/locale/language/export msgid "Language name" msgstr "" #: /admin/locale/language/export msgid "" "Select the language you would like to export in gettext Portable " "Object (.po) format." msgstr "" #: /admin/locale/language/export msgid "Export template" msgstr "" #: /admin/locale/language/export msgid "" "Generate a gettext Portable Object Template (.pot) file with all " "the interface strings from the Drupal locale database.
" msgstr "" #: /admin/locale/language/export msgid "" "This page allows you to export Drupal strings. The first option is " "to export a translation so it can be shared. The second option is to " "generate a translation template, which contains all Drupal strings, " "but without their translations. You can use this template to start a " "new translation using a specialized desktop application.
" msgstr "" #: /admin/filters/1 msgid "'%format' input format" msgstr "" #: /admin/filters/1 msgid "list filters" msgstr "" #: /admin/filters/1 msgid "configure filters" msgstr "" #: /admin/filters/1 msgid "rearrange filters" msgstr "" #: /admin/filters/1 msgid "Legacy filter" msgstr "" #: /admin/filters/1 msgid "" "Allows you to restrict if users can post HTML and which tags to filter " "out." msgstr "" #: /admin/filters/1 msgid "Replaces URLs from Drupal 4.1 (and lower) with updated equivalents." msgstr "" #: /admin/filters/1 msgid "Converts line breaks into HTML (i.e. <br> and <p> tags)." msgstr "" #: /admin/filters/1 msgid "" "Runs a piece of PHP code. The usage of this filter should be " "restricted to administrators only!" msgstr "" #: /admin/filters/1 msgid "Filters" msgstr "Филтри" #: /admin/filters/1 msgid "" "These are the guidelines that users will see for posting in this " "input format. They are automatically generated from the filter " "settings.
" msgstr "" #: /admin/filters/1 msgid "" "\n" "Every filter performs one particular change on the user " "input, for example stripping out malicious HTML or making URLs " "clickable. Choose which filters you want to apply to text in this " "input format.
\n" "If you notice some filters are causing conflicts in the output, you " "can rearrange them." msgstr "" #: /node/add/story msgid "The name %name does not exist." msgstr "" #: /node/add/story msgid "not verified" msgstr "" #: /user/2003/edit msgid "The changes have been saved." msgstr "Промените се зачувани." #: /cron.php msgid "Aggregator: failed to parse RSS feed %site: %error." msgstr "" #: /cron.php msgid "Failed to parse RSS feed %site: %error." msgstr "" #: /poll/vote/1048 msgid "You're not allowed to vote on this poll." msgstr "" #: /admin/taxonomy/image msgid "Recursively displaying images." msgstr "" #: /node/1032/edit msgid "Confirm deletion" msgstr "Потврди бришење" #: /node/1032/edit msgid "%type: deleted %title." msgstr "" #: /node/1032/edit msgid "The node has been deleted." msgstr "Содржината е избришана." #: /admin/settings/throttle msgid "menu" msgstr "" #: /admin/settings/throttle msgid "throttle" msgstr "" #: /admin/settings/throttle msgid "menus" msgstr "менија" #: /admin/settings/throttle msgid "edit menu item" msgstr "" #: /admin/settings/throttle msgid "reset menu item" msgstr "ресетирај предмет од менито" #: /admin/settings/throttle msgid "disable menu item" msgstr "" #: /admin/settings/throttle msgid "delete menu item" msgstr "" #: /admin/settings/throttle msgid "add menu" msgstr "додади мени" #: /admin/settings/throttle msgid "add menu item" msgstr "додади предмет во менито" #: /admin/settings/throttle msgid "reset menus" msgstr "ресетирај ги менијата" #: /admin/settings/throttle msgid "Auto-throttle multiplier" msgstr "" #: /admin/settings/throttle msgid "" "The \"auto-throttle multiplier\" is the number of hits in the past 60 " "seconds required to trigger a higher throttle level. For example, if " "you set the multiplier to 60, and your site is getting less than 60 " "hits a minute, then the throttle will be at a level of 0. Only once " "you start getting more than 60 hits a minute will the throttle level " "go to 1. If you start getting more than 120 hits a minute, the " "throttle becomes 2. This continues until your site is sustaining more " "than 300 hits per minute, at which time the throttle reaches a maximum " "level of 5. In the pop down menu, the first number is the multiplier, " "and the numbers in parenthesis are how many hits are required to " "switch to each throttle level. The more powerful your server, the " "higher you should set the multiplier value." msgstr "" #: /admin/settings/throttle msgid "Auto-throttle probability limiter" msgstr "" #: /admin/settings/throttle msgid "" "The auto-throttle probability limiter is an efficiency mechanism to " "statistically reduce the overhead of the auto-throttle. The limiter " "is expressed as a percentage of page views, so for example if set to " "the default of 10% we only perform the extra database query to update " "the current level 1 out of every 10 page views. The busier your site, " "the lower you should set the limiter value." msgstr "" #: /admin/settings/throttle msgid "Auto-throttle tuning" msgstr "" #: /admin/settings/throttle msgid "" "If your site gets linked to by a popular website, or otherwise comes " "under a \"Denial of Service\" (DoS) attack, your webserver might " "become overwhelmed. This module provides a mechanism for " "automatically detecting a surge in incoming traffic. This mechanism " "is utilized by other Drupal models to automatically optimize their " "performance by temporarily disabling CPU-intensive functionality. To " "use the auto-throttle, the access log must be enabled. It is advised " "that you carefully read the explanations below and then properly tune " "this module based on your site's requirements and your webserver's " "capabilities." msgstr "" #: /user/register msgid "The name %name is already taken." msgstr "" #: /admin/settings msgid "Tue" msgstr "" #: /admin/block msgid "Throttle status" msgstr "" #: /admin/menu msgid "Menu item" msgstr "Предмет од менито" #: /admin/menu msgid "enable" msgstr "вклучи" #: /admin/menu msgid "disabled" msgstr "исклучено" #: /admin/menu msgid "locked" msgstr "заклучено" #: /admin/menu msgid "disable" msgstr "исклучи" #: /admin/menu msgid "" "Select an operation from the list to move, change, or delete a menu " "item." msgstr "" #: /admin/menu/item/edit/23 msgid "The name to display for this link." msgstr "" #: /admin/menu/item/edit/23 msgid "The description displayed when hovering over a menu item." msgstr "" #: /admin/menu/item/edit/23 msgid "The Drupal path this menu item links to." msgstr "" #: /admin/menu/item/edit/23 msgid "Parent item" msgstr "" #: /admin/menu/item/edit/23 msgid "" "Optional. In the menu, the heavier items will sink and the lighter " "items will be positioned nearer the top." msgstr "" #: /admin/settings msgid "Mon" msgstr "" #: /admin/taxonomy/add/vocabulary msgid "" "When you create a controlled vocabulary you are creating a set of " "terms to use for describing content (known as descriptors in indexing " "lingo). Drupal allows you to describe each piece of content (blog, " "story, etc.) using one or many of these terms. For simple " "implementations, you might create a set of categories without " "subcategories, similar to Slashdot.org's or Kuro5hin.org's sections. " "For more complex implementations, you might create a hierarchical list " "of categories." msgstr "" #: /admin/taxonomy/add/vocabulary msgid "Created new vocabulary %name." msgstr "" #: /admin/taxonomy/edit/vocabulary/3 msgid "Updated vocabulary %name." msgstr "" #: /admin/taxonomy/add/term/1 msgid "Created new term %term." msgstr "" #: /admin/taxonomy/edit/vocabulary/3 msgid "deleted vocabulary \"%name\"." msgstr "" #: /admin/modules msgid "An interface for viewing content grouped by arbitrary taxonomy terms." msgstr "" #: /admin/modules msgid "taxonomy_browser" msgstr "" #: /admin/modules msgid "category browser" msgstr "" #: /taxonomy_browser msgid "Advanced category search" msgstr "" #: /taxonomy_browser msgid "" "
You can select multiple items from each list by holding down the "
"Ctrl (Mac: command) key while left-clicking "
"each item.
Users with the correct permissions can send feedback\n" " to the site admin via email from a form on the site.
\n" "To enable its use, a user needs the \"access feedback\" " "permission.
\n" "The site admin specifies the email address that the users " "send to, as well as other\n" " parameters, such as what fields to show the user to fill (name, " "address, email), whether\n" " the user address is to be validated, and whether to log all " "attempts to use this form.
\n" "The email address is never visible to the users, and " "therefore cannot be used by SPAM\n" " harvesters.
" msgstr "" #: /admin/help msgid "feedback" msgstr "" #: /admin/help msgid "locale" msgstr "" #: /admin/help msgid "node" msgstr "" #: /admin/help msgid "" "\n" "The page module is used when you want to create content that " "optionally inserts a link into your navigation system. You can also, " "however, create pages that don't have this link by skipping the link " "text field in the page form. At this time, not all themes support the " "link insertion behavior. Some themes, like xtemplate, provide " "alternative mechanisms for link creation. Pages are also unique in " "that they shortcut the typical lifecycle of user generated content " "(i.e. submit -> moderate -> post -> comment).
\n" "create pages: Allows a role to create pages. " "They cannot edit or delete pages, even if they are the authors. You " "must enable this permission to in order for a role to create a " "page.
\n" "edit own pages: Allows a role to add/edit " "pages if they own the page. Use this permission if you want users to " "be able to edit and maintain their own pages.
\n" " " msgstr "" #: /admin/help msgid "page" msgstr "" #: /admin/help msgid "" "\n" "Users with the correct permissions can create and/or vote on " "polls.
\n" "Creating a poll is much like creating any other node. Click " "\"create poll\" in your user box. The title of the poll should be the " "question, then enter the answers and the \"base\" vote counts. You can " "also choose the time period over which the vote will run.
The Poll item in the navigation links will take you to " "a page where you can see all the current polls, vote on them (if you " "haven't already) and view the results.
" msgstr "" #: /admin/help msgid "poll" msgstr "" #: /admin/help msgid "search" msgstr "" #: /admin/help msgid "" "\n" "The statistics module keeps track of numerous statistics for " "your site but be warned, statistical collection does cause a little " "overhead, thus everything comes disabled by " "default.
\n" "The module counts how many times, and from where -- using " "HTTP referrer -- each of your posts is viewed. Once we have that count " "the module can do the following with it:\n" "
Notes on using the statistics:
\n" "As with any new module, the statistics module needs to be enabled before you can use it. Also refer to " "the permissions section, as this module " "supports four separate permissions.
\n" "This admin page shows you site-wide referrer statistics. You " "can see 'all' statistics, 'external' statistics or " "'internal' statistics. Default is 'all'.
\n" "This admin page gives you an at-a-glance look at your most " "popular content. It is useful for understanding what content on your " "Drupal site is the most popular. Also on this page are links to the " "referrer statistics for each listed node.
\n" "There are some configuration options added to the main administer » settings » " "statistics section:
\n" "This module creates a block that can display the day's top " "viewed content, the all time top viewed content, and the last content " "viewed. Each of these links can be enabled or disabled individually, " "and the number of posts displayed for each can be configured with a " "drop down menu. If you disable all sections of this block, it will " "not appear.
\n" "Don't forget to enable the " "block.
\n" "This module creates a user page that can display summaries of " "the day's most popular viewed content, the all time most popular " "content, and the last content viewed. Each of these summaries can be " "enabled or disabled individually, and the number of posts displayed " "for each can be configured with a drop down menu. You can also assign " "a name for the automatically generated link to the user page. If no " "name is set, the link will not be displayed.
\n" "This module has four permissions that " "need to be configured in the permissions " "section.
\n" "If 'administer statistics' and 'access " "statistics' are both enabled, the user will see a link from each " "node to that node's referrer statistics (if enabled).
" msgstr "" #: /admin/help msgid "statistics" msgstr "" #: /admin/help msgid "" "\n" "The story module lets your users submit articles for " "consideration by the rest of the community, who can vote on them if " "moderation is enabled. Stories usually follow a publishing flow of " "submit -> moderate -> post to the main page -> " "comments. Administrators are able to shortcut this flow as " "desired.
\n" " In administer » settings » " "story you can set up an introductory text for story authors, and a " "floor on the number of words which may be included in a story. This is " "designed to help discourage the submission of trivially short " "stories.\n" "create stories: Allows a role to create " "stories. They cannot edit or delete stories, even if they are the " "authors. You must enable this permission to in order for a role to " "create a story.
\n" "edit own stories: Allows a role to add/edit " "stories if they own the story. Use this permission if you want users " "to be able to edit and maintain their own stories.
\n" " " msgstr "" #: /admin/help msgid "story" msgstr "" #: /admin/help msgid "" "\n" "Drupal comes with system-wide defaults but the setting-module " "provides control over many Drupal preferences, behaviours including " "visual and operational settings.
\n" "Some modules require regularly scheduled actions, such as " "cleaning up logfiles. Cron, which stands for chronograph, is a " "periodic command scheduler executing commands at intervals specified " "in seconds. It can be used to control the execution of daily, weekly " "and monthly jobs (or anything with a period measured in seconds). " "Automating tasks is one of the best ways to keep a system running " "smoothly, and if most of your administration does not require your " "direct involvement, cron is an ideal solution.
\n" "Whenever %cron-link is accessed, cron will run: it calls the " "_cron hook in each module allowing the module to run tasks if they " "have not been executed in the last n seconds, where n is the " "period of that task. When all the tasks are finished, cron is " "done.
\n" "The recommended way to set up your cron system is to set up a " "Unix/Linux crontab entry (see \"man crontab\") that frequently visits " "%cron-link. Note that cron does not guarantee the commands will be " "executed at the specified interval. However, Drupal will try its best " "to run the tasks as close to the specified intervals as possible. The " "more you visit cron.php, the more accurate cron will be.
\n" "If your hosting company does not allow you to set up crontab " "entries, you can always ask someone else to set up an entry for you. " "After all, virtually any Unix/Linux machine with access to the " "internet can set up a crontab entry to frequently visit " "%cron-link.
\n" "For the Unix/Linux crontab itself, use a browser like lynx or wget but make sure "
"the process terminates: either use /usr/bin/lynx -source "
"%base_url/cron.php or /usr/bin/wget -o /dev/null -O "
"/dev/null %cron-link. Take a look at the example scripts in "
"the scripts-directory. Make sure to adjust them to fit "
"your needs. A good crontab line to run the cron script once every "
"hour would be:\n"
"
00 * * * * " "/home/www/drupal/scripts/cron-lynx.sh\n" " Note that it is essential to access
cron.php using "
"a browser on the web site's domain; do not run it using command line "
"PHP and avoid using localhost or 127.0.0.1 "
"or some of the environment variables will not be set correctly and "
"features may not work as expected.\n"
" Drupal has a caching mechanism which stores dynamically " "generated web pages in a database. By caching a web page, Drupal does " "not have to create the page each time someone wants to view it, " "instead it takes only one SQL query to display it, reducing response " "time and the server's load. Only pages requested by \"anonymous\" " "users are cached. In order to reduce server load and save bandwidth, " "Drupal stores and sends cached pages compressed.
" msgstr "" #: /admin/help msgid "system" msgstr "" #: /admin/help msgid "taxonomy" msgstr "" #: /admin/help msgid "taxonomy_image" msgstr "" #: /admin/help msgid "" "\n" "This Drupal module allows you to enable and configure the " "auto-throttle congestion control mechanism offered by the statistics module. The auto-throttle " "mechanism allows your site to automatically adapt to different server " "levels.
\n" "This module also adds a block that displays the current " "status of the throttle. You must have \"access throttle block\" privileges to " "view the block. As a general rule of thumb, only site administrators " "should be granted access to this block.
\n" "The auto-throttle mechanism performs an extra database query " "in order to determine what the current throttle level should be. " "Fortunately the throttle can be tuned so these database queries only " "occur on a fraction of all pages generated by your site, reducing the " "overhead to an insignificant amount. Additionally, when the top-most " "throttle level is reached, all throttle queries are suspended for a " "configurable period of time. More detail follows.
\n" "As with any module, the throttle module needs to be enabled before you can use it. Also " "refer to the permissions section below if you wish to access the " "throttle statistics block.
\n" "The configuration section " "for the throttle allows you to turn it on and off, as well as to " "fine-tune how sensitive it is.
\n" "This first option on the throttle module " "configuration screen allows you to enable or disable the " "auto-throttling mechanism. Note that the access-log must also be " "enabled via the statistics module " "for the auto-throttling mechanism to have any effect.\n" "
\n" "This second option allows you to tune the " "auto-throttle mechanism. The auto-throttle mechanism supports six " "throttle levels, from 0 (off) to 5 (maximum). The current throttle " "level is based upon how many pages have been accessed on your site in " "the past 60 seconds - the more pages being displayed, the higher the " "throttle level. This multiplier defines how many hits are required to " "switch from one throttle level to the next.
\n" "For example, with a throttle multiplier of 20: Once 20 pages " "have been accessed on your site within a period of 60 seconds, the " "throttle level will be incremented to a level of 1. Once 40 pages " "have been accessed on your site within a period of 60 seconds, the " "throttle level will be incremented to a level of 2. And so on, until " "100 pages are accessed on your site within a period of 60 seconds, at " "which time the throttle level will be set to a maximum level of " "5.
\n" "This option allows you to minimize the " "performance impact of the auto-throttle. If we refer to the " "probability limiter as P, then P% of all pages generated by your site " "will perform an extra database query to verify that the current " "throttle level is appropriate to the current server load.
\n" "As a rule of thumb, the higher your multiplier, the lower " "your probability limiter should be. For example, if you have a " "multiplier of 100, then you logically don't need to check the throttle " "level more than once out of every 100 page views, so the probability " "limiter should be set to 1%. As database queries are \"expensive\", " "it's recommended that you keep the probability limiter to the smallest " "percentage possible, while still high enough to react quickly to a " "change in server load.
This block displays some statistics regarding the current " "throttle and its configuration. It is recommended that only site " "administrators receive the \"access " "throttle block\" permission bit required to view this block. It " "does not display information that would interest a normal site " "end-user.
\n" "Don't forget to enable the " "block.
\n" "This module has one permission that needs to be configured in " "user permissions.
\n" "The function throttle_status() will return a "
"number from 0 to 5. 0 means that there is no throttle enabled at this "
"time. Each number above that is a progressively more throttled "
"system... To disable a feature when a site first begins to get busy, "
"disable it at a throttle of 2 or 3. To hold on to the bitter end, "
"wait until 4 or 5.
To implement the throttle, you should do something like " "this:\n" "
\n"
" if (module_invoke(\"throttle\", \"status\") >= "
"$my_throttle_value) {\n"
" // my throttle limit was reached, disable stuff\n"
" }\n"
" else {\n"
" // throttle limit not reached, execute normally\n"
" }\n"
" "
msgstr ""
#: /admin/help
msgid "throttle"
msgstr ""
#: /admin/help
msgid ""
"The tracker module is a handy module for displaying the most recent " "posts. By following the recent posts link in the user block, " "a user may quickly review all recent postings.
" msgstr "" #: /admin/help msgid "tracker" msgstr "" #: /admin/help msgid "user" msgstr "" #: /admin/help msgid "" "The watchdog module monitors your web site, capturing system events " "in a log to be reviewed by an authorized individual at a later time. " "The watchdog log is simply a list of recorded events containing usage " "data, performance data, errors, warnings and operational information. " "It is vital to check the watchdog report on " "a regular basis as it is often the only way to tell what is going " "on.
" msgstr "" #: /admin/help msgid "watchdog" msgstr "" #: /admin/help msgid "" "\n" "This guide explains what the various modules in Drupal do and how to configure them.
\n" "It is not a substitute for the Drupal " "handbook available online and should be used in conjunction with " "it. The online reference handbook might be more up-to-date and has " "helpful user-contributed comments. It is your definitive reference " "point for all Drupal documentation.
\n" "Help is available on the following items:
\n" " %help_pages\n" "A very powerful feature of Drupal is the ability to have control " "over all paths. The path module is the tool that provides this " "functionality and is part of the basic Drupal installation, although " "it is not enabled by default. Some examples of re-mapping paths " "are:
\n" "\n" "user/login => login\n" "\n" "image/tid/16 => store\n" "\n" "taxonomy/term/7+19+20+21 => store/products/whirlygigs\n" "\n" "node/3 => contact\n" "\n" "
This functionality integrates seamlessly into node forms and also " "provides the administrator an interface to view all aliases that have " "been created.
\n" "Aliases have a many to one relationship with their original Drupal " "URLs. In other words you can have many different aliases map to a " "single path. An example of where a multiple aliases come in handy is " "creating a standard RSS feed URL:
\n" "\n" "\n" "node/feed => rss.xml\n" "node/feed => index.rdf\n" "\n" "\n" "
When Drupal generates links for a path with multiple aliases it " "will choose the first alias created per system URL. So in our above " "example, Drupal would use rss.xml as the default alias rather than " "index.rdf. To change this behavior, delete the aliases for node/feed " "and create the index.rdf alias before rss.xml.
\n" "\n" "Two permissions are related to URL aliasing: create url " "aliases and administer url aliases.
\n" "Drupal also comes with user defined mass URL aliasing capabilities. "
"You might like to see completely different URLs used by Drupal, or "
"even URLs translated to the visitors' native language, in which case "
"this feature is handy. Only an administrator with access to the "
"website source code can set up this kind of aliases. You can define a "
"conf_url_rewrite function in conf.php, following this "
"example:
\n"
"function conf_url_rewrite($path, $mode = 'incoming') {\n"
" if ($mode == 'incoming') { // URL coming from a client\n"
" return preg_replace('!^display/(\\d+)$!', 'node/\\1', $path);\n"
" }\n"
" else { // URL going out to a client\n"
" $aliased = preg_replace('!^node/(\\d+)$!', 'display/\\1', "
"$path);\n"
" if ($aliased != $path) { return $aliased; }\n"
" }\n"
"}\n"
"\n"
"This function will shorten every node/$node_id type of "
"URL to display/$node_id. Individual URL aliases defined "
"on the browser interface of Drupal take precedence, so if you have the "
"'contact' page alias from the example above, then the "
"display/3 alias will not be effective when outgoing links "
"are created. Incoming URLs however always work with the mass URL "
"aliased variant. Only the 'incoming' and 'outgoing' modes are supposed "
"to be supported by your conf_url_rewrite function.
You cannot only use this feature to shorten the URLs, or to "
"translate them to you own language, but also to add completely new "
"subURLs to an already existing module's URL space, or to compose a "
"bunch of existing stuff together to a common URL space. You can create "
"a news section for example aliasing nodes and taxonomy "
"overview pages falling under a 'news' vocabulary, thus having "
"news/15 and news/sections/3 instead of "
"node/15 and taxonomy/term/3. You need "
"extensive knowledge of Drupal's inner workings and regular expressions "
"though to make such advanced aliases.
Admins may create many image nodes at once by uploading all images " "to a folder on the server. This upload happens outside of Drupal, " "usually using an FTP client.
" msgstr "" #: /admin/modules msgid "" "Allow users to upload images and to display them in shared and " "personal image galleries." msgstr "" #: /admin/modules msgid "my image gallery" msgstr "моја галерија на слики" #: /admin/modules msgid "display image" msgstr "прикажи слика" #: /admin/modules msgid "directory upload: slow" msgstr "" #: /admin/modules msgid "directory upload: fast" msgstr "" #: /admin/settings/image msgid "" "This text will be displayed at the top of the image submission form. " "It is useful for helping or instructing your users." msgstr "" #: /admin/settings/image msgid "Default image path" msgstr "Стандардна патека за слики" #: /admin/settings/image msgid "" "Default path for uploaded images relative to your Drupal installation; " "it must be writeable and visible from the web. Don't forget the slash " "(/) at the end." msgstr "" #: /admin/settings/image msgid "Default thumb path" msgstr "Стандардна патека за сликички" #: /admin/settings/image msgid "" "Default path for thumbnails relative to your Drupal installation; it " "must be writeable and visible from the web. Don't forget the slash (/) " "at the end." msgstr "" #: /admin/settings/image msgid "Temporary image path" msgstr "Привремена патека за слики" #: /admin/settings/image msgid "" "Path for working directory relative to your Drupal installation; it " "must be writeable and visible from the web. Don't forget the slash (/) " "at the end." msgstr "" #: /admin/settings/image msgid "Maximum temporary image directory size" msgstr "" #: /admin/settings/image msgid "MBytes." msgstr "" #: /admin/settings/image msgid "Stored images filenames" msgstr "" #: /admin/settings/image msgid "" "The filename of an image stored on the server could be based on an " "unique random string or include the original filename. In the later " "case, the node id will be appended to the filename." msgstr "" #: /admin/settings/image msgid "Default max image size" msgstr "" #: /admin/settings/image msgid "KBytes." msgstr "" #: /admin/settings/image msgid "Default max image resolution" msgstr "" #: /admin/settings/image msgid "Example: 800x600." msgstr "" #: /admin/settings/image msgid "List of valid resolutions" msgstr "" #: /admin/settings/image msgid "" "This is a list of resolutions that the image can be displayed at as " "well as its original size" msgstr "" #: /admin/settings/image msgid "Default image display resolution" msgstr "" #: /admin/settings/image msgid "" "Select a resolution that you wish the image to be displayed at if no " "resolution is specified." msgstr "" #: /admin/settings/image msgid "Specify resolutions that will be generated at time of editing." msgstr "" #: /admin/settings/image msgid "" "This is a list of the resolutions that will be created at the time of " "editing. Ones not selected will generated and saved the first time " "they are displayed." msgstr "" #: /admin/settings/image msgid "Default thumbnail resolution" msgstr "" #: /admin/settings/image msgid "" "Default size of thumbnails: format will be the same as original image. " "Use just one dimension, and put a \"x\" to specify height. Examples: " "\"100\" for width of 100; \"x200\" for height of 200." msgstr "" #: /admin/settings/image msgid "Image library" msgstr "Библиотека на слики" #: /admin/settings/image msgid "" "Select the image library to be used during thumbnail generation and " "image manipulation. Use ImageMagick if you can; GD produces worse " "thumbnails, might not support GIF and this module doesn't support " "image editing (rotate, crop etc) with it." msgstr "" #: /admin/settings/image msgid "Imagemagick Convert path" msgstr "" #: /admin/settings/image msgid "" "Absolute path to ImageMagick convert file. Include the 'convert.exe' " "(or other filename) at the end. Leave it blank if you have selected GD " "library." msgstr "" #: /admin/settings/image msgid "Background Color" msgstr "" #: /admin/settings/image msgid "Color used to fill in background when rotating images." msgstr "" #: /admin/settings/image msgid "jhead path" msgstr "" #: /admin/settings/image msgid "Absolute path of jhead, for EXIF parsing; blank to disable." msgstr "" #: /admin/settings/image msgid "Imagemagick and GD are supported image libraries. Imagemagick is " "required for full image manipulation features and is suggested for " "better thumbnail quality.
\n" "Many ISPs already have Imagemagick installed and available " "for your use. If you are hosted on Linux and have shell access, type " "which convert at the command prompt This will tell you where " "the binary is, if it is in the path. The name of the binary on most " "unixoid systems is simply convert.
\n" "If you choose to use the GD library, you should install " "version 2.0 or higher. However, version 1.x of the GD library is " "supported, even if it produces lower quality images. In order to use " "GD PHP must be compiled with GD enabled.
\n" "JPEG images may be tagged with information about the image. " "This information talks about the caption, headline, creation date, " "location, and many other parameters about the image. To embed IPTC " "data in your images, use an IPTC aware editor like PixVue (free, Windows only), Photoshop (commercial, Windows/Mac), or possibly GIMP (Linux, Unix, Windows).
\n" "This module reads any IPTC info in your image, and uses it " "appropriately. Fast directory upload of IPTC images is the quickest " "and most complete way to add lots of images into Drupal. Further, you " "may tag your images while offline and only go online to do the " "upload/creation in Drupal.
\n" "JPEG images may also be tagged with information about the " "camera settings used to take the picture.
\n" "This module can read EXIF information about your images via " "jhead.
\n" "All directories must be readable and writeable for the user " "id that the web server runs under.
\n" "You can verify your directory and image library application " "configuration by visiting the images " "administration screen.
" msgstr "" #: /admin/settings/image msgid "image galleries" msgstr "" #: /admin/image/dir_upload/fast msgid "Directory to scan" msgstr "" #: /admin/image/dir_upload/fast msgid "" "The path to the directory which holds the source image files. This " "path should be relative to Drupal root directory - don't forget the " "slash (/) at the end." msgstr "" #: /admin/image/dir_upload/fast msgid "Delete images after insert" msgstr "" #: /admin/image/dir_upload/fast msgid "" "If instructed, Drupal will delete all files in the above directory " "after creating the image nodes." msgstr "" #: /admin/image/dir_upload/fast msgid "Add new gallery" msgstr "Додај нова галерија" #: /admin/image/dir_upload/fast msgid "" "If needed, create a new term for this gallery by clicking on one of " "these vocabularies" msgstr "" #: /admin/image/dir_upload/fast msgid "Directory upload" msgstr "" #: /admin/image/dir_upload/fast msgid "" "\n" "Most programs are written and documented in English, and " "primarily use English to interact with users. This is also true for a " "great deal of web sites. However, most people are less comfortable " "with English than with their native language, and would prefer to use " "their mother tongue as much as possible. Many people love to see their " "web site showing a lot less English, and far more of their own " "language. Therefore Drupal provides a framework to setup a " "multi-lingual web site, or to overwrite the default English " "texts.
\n" "Whenever Drupal encounters an interface string which needs to " "be displayed, it tries to translate it into the currently selected " "language. If a translation is not available, then the string is " "remembered, so you can look up untranslated strings easily.
\n" "Drupal provides two options to translate these strings. First " "is the integrated web interface, where you can search for untranslated " "strings, and specify their translations via simple web forms. An " "easier, and much less time consuming method is to import translations " "already done for your language. This is achieved by the use of GNU " "gettext Portable Object files. These are editable with quite " "convenient desktop editors specifically architected for supporting " "your work with GNU Gettext files. The import feature allows you to add " "strings from such files into the site database. The export " "functionality enables you to share your translations with others, " "generating Portable Object files from your site strings." msgstr "" #: /admin/locale/string/search msgid "" "
It is often more convenient to get the strings of your setup on the " "export page, and start with a desktop Gettext " "translation editor though. Here you can search in the translated and " "untranslated strings, and the default English texts provided by " "Drupal.
" msgstr "" #: /node msgid "%count new comments" msgstr "%count нови коментари" #: /admin/comment/delete/2007 msgid "Do you want to delete this comment and all its replies?" msgstr "" #: /admin/comment/delete/2007 msgid "The comment and all its replies have been deleted." msgstr "" #: /admin/comment/delete/2007 msgid "Comment: deleted %subject." msgstr "" #: /admin/logs/warning msgid "" "Watchdog events that don't stop normal operation, but are things you " "should know." msgstr "" #: /admin/logs/regular msgid "Watchdog events that are \"normal\" and have no other classification." msgstr "" #: /admin/taxonomy/edit/vocabulary/5 msgid "Delete vocabulary \"%name\"" msgstr "" #: /admin/taxonomy/edit/vocabulary/5 msgid "Are you sure you want to delete the vocabulary and all its terms?" msgstr "" #: /admin/path msgid "" "\n" "A very powerful feature of Drupal is the ability to have control " "over all paths. The path module is the tool that provides this " "functionality and is part of the basic Drupal installation, although " "it is not enabled by default. Some examples of re-mapping paths " "are:
\n" "\n" "user/login => login\n" "\n" "image/tid/16 => store\n" "\n" "taxonomy/term/7+19+20+21 => store/products/whirlygigs\n" "\n" "node/3 => contact\n" "\n" "
This functionality integrates seamlessly into node forms and also " "provides the administrator an interface to view all aliases that have " "been created.
\n" "Aliases have a many to one relationship with their original Drupal " "URLs. In other words you can have many different aliases map to a " "single path. An example of where a multiple aliases come in handy is " "creating a standard RSS feed URL:
\n" "\n" "\n" "node/feed => rss.xml\n" "node/feed => index.rdf\n" "\n" "\n" "
When Drupal generates links for a path with multiple aliases it " "will choose the first alias created per system URL. So in our above " "example, Drupal would use rss.xml as the default alias rather than " "index.rdf. To change this behavior, delete the aliases for node/feed " "and create the index.rdf alias before rss.xml.
\n" "\n" "Two permissions are related to URL aliasing: create url " "aliases and administer url aliases.
\n" "Drupal also comes with user defined mass URL aliasing capabilities. "
"You might like to see completely different URLs used by Drupal, or "
"even URLs translated to the visitors' native language, in which case "
"this feature is handy. Only an administrator with access to the "
"website source code can set up this kind of aliases. You can define a "
"conf_url_rewrite function in conf.php, following this "
"example:
\n"
"function conf_url_rewrite($path, $mode = 'incoming') {\n"
" if ($mode == 'incoming') { // URL coming from a client\n"
" return preg_replace('!^display/(\\d+)$!', 'node/\\1', $path);\n"
" }\n"
" else { // URL going out to a client\n"
" $aliased = preg_replace('!^node/(\\d+)$!', 'display/\\1', "
"$path);\n"
" if ($aliased != $path) { return $aliased; }\n"
" }\n"
"}\n"
"\n"
"This function will shorten every node/$node_id type of "
"URL to display/$node_id. Individual URL aliases defined "
"on the browser interface of Drupal take precedence, so if you have the "
"'contact' page alias from the example above, then the "
"display/3 alias will not be effective when outgoing links "
"are created. Incoming URLs however always work with the mass URL "
"aliased variant. Only the 'incoming' and 'outgoing' modes are supposed "
"to be supported by your conf_url_rewrite function.
You cannot only use this feature to shorten the URLs, or to "
"translate them to you own language, but also to add completely new "
"subURLs to an already existing module's URL space, or to compose a "
"bunch of existing stuff together to a common URL space. You can create "
"a news section for example aliasing nodes and taxonomy "
"overview pages falling under a 'news' vocabulary, thus having "
"news/15 and news/sections/3 instead of "
"node/15 and taxonomy/term/3. You need "
"extensive knowledge of Drupal's inner workings and regular expressions "
"though to make such advanced aliases.
The statistics module keeps track of numerous statistics for " "your site but be warned, statistical collection does cause a little " "overhead, thus everything comes disabled by " "default.
\n" "The module counts how many times, and from where -- using " "HTTP referrer -- each of your posts is viewed. Once we have that count " "the module can do the following with it:\n" "
Notes on using the statistics:
\n" "As with any new module, the statistics module needs to be enabled before you can use it. Also refer to " "the permissions section, as this module " "supports four separate permissions.
\n" "This admin page shows you site-wide referrer statistics. You " "can see 'all' statistics, 'external' statistics or " "'internal' statistics. Default is 'all'.
\n" "This admin page gives you an at-a-glance look at your most " "popular content. It is useful for understanding what content on your " "Drupal site is the most popular. Also on this page are links to the " "referrer statistics for each listed node.
\n" "There are some configuration options added to the main administer » settings » " "statistics section:
\n" "This module creates a block that can display the day's top " "viewed content, the all time top viewed content, and the last content " "viewed. Each of these links can be enabled or disabled individually, " "and the number of posts displayed for each can be configured with a " "drop down menu. If you disable all sections of this block, it will " "not appear.
\n" "Don't forget to enable the " "block.
\n" "This module creates a user page that can display summaries of " "the day's most popular viewed content, the all time most popular " "content, and the last content viewed. Each of these summaries can be " "enabled or disabled individually, and the number of posts displayed " "for each can be configured with a drop down menu. You can also assign " "a name for the automatically generated link to the user page. If no " "name is set, the link will not be displayed.
\n" "This module has four permissions that " "need to be configured in the permissions " "section.
\n" "If 'administer statistics' and 'access " "statistics' are both enabled, the user will see a link from each " "node to that node's referrer statistics (if enabled).
" msgstr "" #: /admin/help msgid "" "\n" "This guide explains what the various modules in Drupal do and how to configure them.
\n" "It is not a substitute for the Drupal " "handbook available online and should be used in conjunction with " "it. The online reference handbook might be more up-to-date and has " "helpful user-contributed comments. It is your definitive reference " "point for all Drupal documentation.
\n" "Help is available on the following items:
\n" " %help_pages\n" "The forum module uses taxonomy to organize itself. To create " "a forum you first have to create a taxonomy " "vocabulary. When doing this, choose a sensible name for it (such " "as \"fora\") and make sure under \"Types\" that \"forum\" is selected. " "Once you have done this, add some terms to " "it. Each term will become a forum. If you fill in the description " "field, users will be given additional information about the forum on " "the main forum page. For example: \"troubleshooting\" - \"Please ask " "your questions here.\"
\n" "When you are happy with your vocabulary, go to administer » settings » forum and set " "Forum vocabulary to the one you have just created. " "There will now be fora active on the site. For users to access them " "they must have the \"access content\" permission and to create a topic they must " "have the \"create forum topics\" permission. These permissions can be set in " "the permission pages.
\n" "To disable icons, set the icon path as blank in administer » settings » forum.
\n" "All files in the icon directory are assumed to be images. You " "may use images of whatever size you wish, but it is recommended to use " "15x15 or 16x16.
" msgstr "" #: /admin/user/configure/permission msgid "create forum topics" msgstr "креирај теми на форумот" #: /admin/logs/hits/pages msgid "Top pages in the past %interval" msgstr "" #: /admin/logs/hits/pages msgid "This page shows access statistics for each page of your website." msgstr "" #: /user/289/edit msgid "Upload picture" msgstr "" #: /user/289/edit msgid "" "Your virtual face or picture. Maximum dimensions are %dimensions and " "the maximum size is %size kB." msgstr "" #: /user/289/edit msgid "Picture" msgstr "" #: /user/289 msgid "%user's picture" msgstr "" #: /forum msgid "Post new forum topic." msgstr "Отвори нова тема." #: /forum msgid "%time ago