# Translation of Plugins - CloudSearch - Development (trunk) in Danish
# This file is distributed under the same license as the Plugins - CloudSearch - Development (trunk) package.
msgid ""
msgstr ""
"PO-Revision-Date: 2023-04-02 06:58:43+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: GlotPress/4.1.0\n"
"Language: da_DK\n"
"Project-Id-Version: Plugins - CloudSearch - Development (trunk)\n"

#: admin/cloud-search-admin-settings.php:46
msgid "AWS Session token"
msgstr ""

#: admin/cloud-search-admin-docs.php:130
msgid "Using the \"acs_search_args\" filter hook you can programmatically modify (if you need to define a custom expression on the fly when certain conditions are met) the \"$search_args\" right before the query is sent to Amazon."
msgstr ""

#: admin/cloud-search-admin-docs.php:129
msgid "Modify search arguments"
msgstr ""

#: admin/cloud-search-admin-docs.php:382
msgid "AMP pages actually supports autocomplete, but need that the results array have to be in a different format. A top level key as \"items\" is needed, otherwise with \"results\" as top level key it doesn't work. For enabling AMP new top level key within results you have to provide an \"amp\" parameter to the API."
msgstr ""

#: admin/cloud-search-admin-docs.php:381
msgid "Work with AMP"
msgstr ""

#: admin/cloud-search-admin-docs.php:379
msgid "This service provides to you a way for searching items, retrieved from the provided input keyword."
msgstr ""

#: admin/cloud-search-admin-docs.php:91
msgid "Using this filter you can add some filter query conditions for filtering additional fields not covered in configuration."
msgstr ""

#: admin/cloud-search-admin-docs.php:90
msgid "Add filter query conditions"
msgstr ""

#: admin/cloud-search-admin-settings.php:227
msgid "Enter comma separated list of fields to be converted to \"date\" in CloudSearch."
msgstr ""

#: admin/cloud-search-admin-settings.php:223
msgid "Date fields"
msgstr ""

#: admin/cloud-search-admin-docs.php:376
msgid "This service provides to you a list of suggested items, retrieved from the provided input keyword. This API is also used for the suggestion feature in the templates."
msgstr ""

#: admin/cloud-search-admin-help.php:203
msgid "You can provide a list of custom legacy post types, separated by \",\", for adding those post types to searches."
msgstr ""

#: admin/cloud-search-admin-settings.php:654
msgid "Enter comma separated list of types if you want to include some legacy post types in searches."
msgstr ""

#: admin/cloud-search-admin-settings.php:650
msgid "List of legacy post types to be included in searches"
msgstr ""

#: templates/cloud-search-content-twentytwenty.php:227
msgid "Pages:"
msgstr ""

#: templates/cloud-search-content-twentytwenty.php:227
msgid "Page"
msgstr ""

#: templates/cloud-search-content-twentytwenty.php:185
msgid "Formats"
msgstr ""

#: templates/cloud-search-content-twentytwenty.php:152
msgid "Post date"
msgstr ""

#. translators: %s: Author name
#: templates/cloud-search-content-twentytwenty.php:128
msgid "By %s"
msgstr ""

#: templates/cloud-search-content-twentytwenty.php:121
msgid "Post author"
msgstr ""

#: admin/cloud-search-admin-docs.php:70
msgid "Perform a documents delete operation"
msgstr ""

#: admin/cloud-search-admin-docs.php:67
msgid "Perform a documents sync operation"
msgstr ""

#: admin/cloud-search-admin-docs.php:64
msgid "Perform an indexing operation (works only if no other index process are running and if an indexing is really needed)"
msgstr ""

#: admin/cloud-search-admin-docs.php:61
msgid "Perform a create/update index operation"
msgstr ""

#: admin/cloud-search-admin-docs.php:58
msgid "Here you can find a list of available commands:"
msgstr ""

#: admin/cloud-search-admin-docs.php:57
msgid "The plugin adds some basic WP CLI commands. The main advantage of the CLI is that you can run a query/sync/index without any AWS execution time limits that you could find using the admin pages."
msgstr ""

#: admin/cloud-search-admin-docs.php:78
msgid "By default, a post is indexed only when published. If you want to index posts that are in other statuses (e.g. \"future\") like when published you can override the default behavior with a filter hook that tells the plugin which statuses are allowed."
msgstr ""

#: admin/cloud-search-admin-docs.php:77
msgid "Add allowed statuses in post transition"
msgstr ""

#. translators: %s: Name of current post. Only visible to screen readers.
#: templates/cloud-search-content-twentynineteen.php:195
msgid "Edit <span class=\"screen-reader-text\">%s</span>"
msgstr ""

#: templates/cloud-search-content-twentynineteen.php:169
msgid "Tags:"
msgstr ""

#: templates/cloud-search-content-twentynineteen.php:156
msgid "Posted in"
msgstr ""

#: templates/cloud-search-content-twentynineteen.php:118
msgid "Posted by"
msgstr ""

#: admin/cloud-search-admin-settings.php:673
msgid "Hide \"Import / Export\" section from menu"
msgstr ""

#: admin/cloud-search-admin-import.php:84
msgid "Import plugin settings from a JSON file. This file can be obtained by exporting the settings on another site using the form above."
msgstr ""

#: admin/cloud-search-admin-import.php:81
#: admin/cloud-search-admin-import.php:91
msgid "Import"
msgstr ""

#: admin/cloud-search-admin-import.php:68
msgid "Export plugin settings for this site as a JSON file. This allows you to easily import the configuration into another site."
msgstr ""

#: admin/cloud-search-admin-import.php:65
#: admin/cloud-search-admin-import.php:74
msgid "Export"
msgstr ""

#: admin/cloud-search-admin-import.php:55
msgid "No settings found"
msgstr ""

#: admin/cloud-search-admin-import.php:45
msgid "Yes"
msgstr ""

#: admin/cloud-search-admin-import.php:16
msgid "Current settings"
msgstr ""

#: admin/cloud-search-admin-import.php:13
msgid "In this page you can import / export the plugin settings. This allows you to easily import the configuration into another site."
msgstr ""

#: admin/cloud-search-admin-import.php:10 admin/cloud-search-admin.php:34
#: admin/cloud-search-admin.php:43
msgid "Import / Export"
msgstr ""

#: actions/cloud-search-action-import.php:43
msgid "Please upload a file to import"
msgstr ""

#: actions/cloud-search-action-import.php:37
msgid "Please upload a valid .json file"
msgstr ""

#: admin/cloud-search-admin-settings.php:245
msgid "Enter comma separated list of fields to be created/managed as \"Sortable\" in CloudSearch."
msgstr ""

#: admin/cloud-search-admin-settings.php:241
msgid "Sortable fields"
msgstr ""

#: admin/cloud-search-admin-settings.php:236
msgid "Enter comma separated list of fields to be converted to \"literal\" in CloudSearch."
msgstr ""

#: admin/cloud-search-admin-settings.php:232
msgid "Literal fields"
msgstr ""

#: admin/cloud-search-admin-settings.php:218
msgid "Enter comma separated list of fields to be converted to \"double\" in CloudSearch."
msgstr ""

#: admin/cloud-search-admin-settings.php:214
msgid "Double fields"
msgstr ""

#: admin/cloud-search-admin-settings.php:209
msgid "Enter comma separated list of fields to be converted to \"int\" in CloudSearch."
msgstr ""

#: admin/cloud-search-admin-settings.php:205
msgid "Integer fields"
msgstr ""

#: admin/cloud-search-admin-settings.php:200
msgid "This management works also if the fields have not been already created, but remember to perform an update index after any change."
msgstr ""

#: admin/cloud-search-admin-settings.php:199
msgid "You have the opportunity to mark as sortable some custom fields. In this sub-section you have to configure your custom fields forcing their type, if int, double, date or literal, and defining which fields should be defined as \"Sortable\" in CloudSearch (by default custom fields are created as text not sortable). This operation is important because text fields don't always sort well. For this reason, you have to provide a comma separated list of custom fields (especially if the original values are integers, doubles or dates)."
msgstr ""

#: admin/cloud-search-admin-settings.php:197
msgid "Custom fields management"
msgstr ""

#: admin/cloud-search-admin-help.php:202
msgid "You can provide a list of invalid chars (for example Unicode chars), separated by \"|\", that will be removed from your documents before syncing them into the CloudSearch index."
msgstr ""

#: admin/cloud-search-admin-help.php:274 admin/cloud-search-admin-help.php:313
msgid "Text Processing in Amazon CloudSearch"
msgstr ""

#: admin/cloud-search-admin-help.php:273
msgid "You can find the list of all the available languages for CloudSearch"
msgstr ""

#: admin/cloud-search-admin-help.php:271
msgid "Use defaults: as last option, the plugin use a \"Multi-language\" setting as default"
msgstr ""

#: admin/cloud-search-admin-help.php:270
msgid "Use the WordPress locale: if no constant is defined the plugin takes automatically the same language of your WordPress installation"
msgstr ""

#: admin/cloud-search-admin-help.php:269
msgid "Use a constant: define in your \"wp-config.php\" the constant \"WP_ACS_SCHEMA_LANGUAGE\" with the desired language"
msgstr ""

#: admin/cloud-search-admin-help.php:267
msgid "You can choose the Analysis schema language for the CloudSearch index in three ways:"
msgstr ""

#: admin/cloud-search-admin-help.php:29 admin/cloud-search-admin-help.php:265
msgid "Manage languages"
msgstr ""

#: cloud-search-hooks.php:105
msgid "Error managing delete transitions for term"
msgstr ""

#: cloud-search-hooks.php:73
msgid "Error managing save transitions for term"
msgstr ""

#: admin/cloud-search-admin-settings.php:369
msgid "show a custom field in the results (after content)"
msgstr ""

#: admin/cloud-search-admin-settings.php:361
msgid "for terms"
msgstr ""

#: admin/cloud-search-admin-settings.php:325
msgid "for posts"
msgstr ""

#: admin/cloud-search-admin-settings.php:182
msgid "With these options you can choose if you want to perform searches also in the selected taxonomies."
msgstr ""

#: admin/cloud-search-admin-settings.php:161
msgid "Searchable taxonomies"
msgstr ""

#: admin/cloud-search-admin-settings.php:96
msgid "Removing an entry within the settings, in the CloudSearch index no field/property will be deleted and values will be maintained without any modification."
msgstr ""

#: admin/cloud-search-admin-manage.php:168
msgid "use this action to perform a sync operation from your WordPress database to your CloudSearch index. You can put a single document to the index (providing the post ID and selecting \"post\" as type for generic posts or custom post types, otherwise providing the term ID and selecting the taxonomy name for the provided ID) or the entire set of your site documents according with the post, field and taxonomy types configured in the settings section."
msgstr ""

#: admin/cloud-search-admin-help.php:192
msgid "The highlights features are available also for term results."
msgstr ""

#: admin/cloud-search-admin-help.php:188
msgid "Sort for terms searches is only related to relevance (_score) because in terms table there is no reference to date information."
msgstr ""

#: admin/cloud-search-admin-help.php:145
msgid "The default term \"category\" is synchronized by default on CloudSearch. You have to select the \"Taxonomy types\" in the \"Schema settings\" to synchronize other custom terms. All the terms are by default not searchable, if you want to search also terms you have to select the desired terms in the \"Searchable taxonomies\" field in the \"Schema settings\" ."
msgstr ""

#: admin/cloud-search-admin-docs.php:484
msgid "The \"acs_api_search_full\" API JSON response does not change. It contains an array of object that represent the results."
msgstr ""

#: admin/cloud-search-admin-docs.php:469
msgid "to an array of object composed by the entity ID and the entity type (\"post\" or \"term\")"
msgstr ""

#: admin/cloud-search-admin-docs.php:460
msgid "The \"acs_api_search\" API JSON response change from an array of IDs"
msgstr ""

#: admin/cloud-search-admin-docs.php:459
msgid "Added support for terms, the APIs results change not returning an IDs array but an object array (with ID and type fields)."
msgstr ""

#: admin/cloud-search-admin-docs.php:458
msgid "What's new with terms?"
msgstr ""

#: admin/cloud-search-admin-settings.php:309
msgid "Customize search page CSS here."
msgstr ""

#: admin/cloud-search-admin-settings.php:305
msgid "Custom CSS"
msgstr ""

#: admin/cloud-search-admin-manage.php:93
msgid "Stop"
msgstr ""

#: admin/cloud-search-admin-docs.php:105
msgid "If you want to enable plugin filters for WooCommerce product tags and EDD tags (not categories), just put the following code in a custom plugin or in the functions.php of your theme."
msgstr ""

#: admin/cloud-search-admin-docs.php:104
msgid "Enabling filters for WooCommerce product tags and EDD tags"
msgstr ""

#: admin/cloud-search-admin-docs.php:22
msgid "Filters"
msgstr ""

#: admin/cloud-search-admin-settings.php:339
msgid "show a custom field in the results (after content and excerpt)"
msgstr ""

#: admin/cloud-search-admin-settings.php:338
#: admin/cloud-search-admin-settings.php:368 cloud-search-utils.php:591
msgid "Custom field"
msgstr ""

#: admin/cloud-search-admin-docs.php:146
msgid "If you want to override search template maintaining the \"Use plugin search page\" functionality you only need to create a new template file named \"cloud-search-template.php\" under a \"templates\" folder in your theme. In this way you can customize the search page container template (not the single result items)."
msgstr ""

#: admin/cloud-search-admin-docs.php:144
msgid "Override search template"
msgstr ""

#: admin/cloud-search-admin-help.php:126
msgid "To better configure CloudSearch client you can modify some client's options by defining the related constants in the wp-config.php file. If not provided, default values are used. You have these possible options:"
msgstr ""

#: admin/cloud-search-admin-settings.php:410
msgid "You can assign weights to selected fields so you can boost the relevance _score of documents with matches in key fields and minimize the impact of matches in less important fields. For example, if you want matches within the post_title field to score higher than matches within the post_content field, you could set the weight of the post_title field to 2 and the weight of the post_content field to 0.5, like the following example (use \",\" as separator without inserting spaces between values):"
msgstr ""

#: admin/cloud-search-admin-settings.php:406
msgid "Field weights"
msgstr ""

#: admin/cloud-search-admin-help.php:312
msgid "Amazon CloudSearch weighting fields"
msgstr ""

#: admin/cloud-search-admin-help.php:262
msgid "Unfortunately, CloudSearch does not currently support nested JSON (object arrays)."
msgstr ""

#: admin/cloud-search-admin-help.php:175
msgid "Fields weighting works well with \"simple\" and \"lucene\" query parsers. The fields option defines the set of fields that are searched by default if you use the simple query parser or don't specify a field in part of a compound expression when using the structured query parser."
msgstr ""

#: admin/cloud-search-admin-help.php:173
msgid "You can assign weights to selected fields so you can boost the relevance _score of documents with matches in key fields, and minimize the impact of matches in less important fields. By default all fields have a weight of 1. Field weights are set with the q.options fields option. You specify fields as an array of strings. To set the weight for a field, you append a caret (^) and a positive numeric value to the field name. You cannot set a field weight to zero or use mathematical functions or expressions to define a field weight. For example, if you want matches within the post_title field to score higher than matches within the post_content field, you could set the weight of the post_title field to 2 and the weight of the post_content field to 0.5:"
msgstr ""

#: admin/cloud-search-admin-manage.php:160
msgid "Update document"
msgstr ""

#: admin/cloud-search-admin-manage.php:158
msgid "Value"
msgstr ""

#: admin/cloud-search-admin-manage.php:156
msgid "Field"
msgstr ""

#: admin/cloud-search-admin-manage.php:152
msgid "Are you sure to update the document?"
msgstr ""

#: admin/cloud-search-admin-manage.php:152
msgid "Invalid values"
msgstr ""

#: admin/cloud-search-admin-manage.php:150
msgid "use this action to perform an update operation to a specific document field of your CloudSearch index. You have to provide the unique document ID, a field name and a field value. If all data are valid, a synchronous task will update the document (if founded) modifying the field value according to the provided one."
msgstr ""

#: admin/cloud-search-admin-manage.php:149
msgid "Update documents"
msgstr ""

#: admin/cloud-search-admin-settings.php:618
msgid "Add also private fields to avoid automatically exclusion (e.g. add \"_price\" to show private field \"price\" in the field types list)."
msgstr ""

#: admin/cloud-search-admin-help.php:303
msgid "Yes, you can use API for retrieve facet information."
msgstr ""

#: admin/cloud-search-admin-help.php:302
msgid "Supports facets?"
msgstr ""

#: admin/cloud-search-admin-help.php:289
msgid "By querying the first two API you can retrieve facet information about your data."
msgstr ""

#: admin/cloud-search-admin-docs.php:290
msgid "Faceting"
msgstr ""

#: admin/cloud-search-admin-docs.php:283
msgid "Reading the facets information in the response, you can refine search query adding a filter query on some fields. For example, the API request URL can be modified to filter only \"page\" post types."
msgstr ""

#: admin/cloud-search-admin-docs.php:282
msgid "Note that if no facets parameters are provided the response JSON is composed only by the array of items/results without the two fields \"items\" and \"facets\"."
msgstr ""

#: admin/cloud-search-admin-docs.php:211
msgid "According to the \"format\" parameter you can get an XML or JSON response that looks like the following code:"
msgstr ""

#: admin/cloud-search-admin-docs.php:202
msgid "Keep in mind that facets works only with API. In other words, the above URL is composed by the parameters:"
msgstr ""

#: admin/cloud-search-admin-docs.php:199
msgid "Here an example for retrieving facet information about fields \"post_type\", \"post_format\" and \"post_status\". The API request URL should be:"
msgstr ""

#: admin/cloud-search-admin-docs.php:198
msgid "An example"
msgstr ""

#: admin/cloud-search-admin-docs.php:195
msgid "You can specify facet options to control the sorting of the facet values for each field, limit the number of facet values returned, or choose what facet values to count and return."
msgstr ""

#: admin/cloud-search-admin-docs.php:194
msgid "You can get facet information for any facet-enabled field by specifying the facet.FIELD parameter in an API search request. By default, Amazon CloudSearch returns facet counts for the top 10 values."
msgstr ""

#: admin/cloud-search-admin-docs.php:192
msgid "How use it"
msgstr ""

#: admin/cloud-search-admin-docs.php:189
msgid "Returns facet information for particular facet values or ranges."
msgstr ""

#: admin/cloud-search-admin-docs.php:188
msgid "Returns facet information sorted either by facet counts or facet values."
msgstr ""

#: admin/cloud-search-admin-docs.php:185
msgid "You can retrieve facet information in two ways:"
msgstr ""

#: admin/cloud-search-admin-docs.php:184
msgid "A facet is an index field that represents a category that you want to use to refine and filter search results."
msgstr ""

#: admin/cloud-search-admin-docs.php:20
msgid "Facets"
msgstr ""

#: admin/cloud-search-admin-settings.php:666
msgid "Hide \"Documentation\" section from menu"
msgstr ""

#: admin/cloud-search-admin-settings.php:662
#: admin/cloud-search-admin-settings.php:669
#: admin/cloud-search-admin-settings.php:676
msgid "Hide page from menu."
msgstr ""

#: admin/cloud-search-admin-settings.php:659
msgid "Hide \"Help\" section from menu"
msgstr ""

#: admin/cloud-search-admin-help.php:204
msgid "Finally, you can choose if you want to hide \"Help\" and \"Documentation\" sections from admin menu."
msgstr ""

#: admin/cloud-search-admin-help.php:118
msgid "To increase security you can store the Amazon access keys in the wp-config.php file and hide them from the plugin settings. Note that is just for this plugin and not for Amazon Web Services. You have to define until 5 constants in this way:"
msgstr ""

#: admin/cloud-search-admin-docs.php:141
msgid "The custom field should be named \"acs_exclude\" with a value \"1\"."
msgstr ""

#: admin/cloud-search-admin-docs.php:140
msgid "If you want to exclude posts or pages from search results (eg: \"contacts\" page, \"thank you\" page, etc) you can add a simple custom field to post/page. In this way you can exclude them permanently so when you go to sync the index or update a post/page, the excluded posts are not indexed."
msgstr ""

#: admin/cloud-search-admin-docs.php:138
msgid "Index posts/pages exclusions"
msgstr ""

#: admin/cloud-search-admin-docs.php:435
msgid "Where \"type_field\" could be \"all\" for searching in all the fields or a specific field name, \"sort_field\" could be \"_score\", \"post_date_gmt\", \"post_modified_gmt\" or \"id\" for sorting results by relevance, by published date, by modified date or by ID, \"sort_order\" could \"desc\" or \"asc\" for view results in descending or ascending order and \"extras\" is an array that could contain a list of attributes that can be provided as input and get back (without any variation) as output from the service. This is useful to pass parameters through service and templates (eg: search content templates could not read global variables (different scopes), with this parameter you can pass data from search page to every single result item template). If you want to sort data on more than one field you can provide an array of values for \"sort_field\" and \"sort_order\" fields. Only if the 2 arrays have the same number of items the sort clause will be composed with multiple values."
msgstr ""

#: admin/cloud-search-admin-settings.php:594
msgid "Blog ID"
msgstr ""

#: admin/cloud-search-admin-settings.php:589
#: admin/cloud-search-admin-settings.php:598
msgid "Leave empty for default."
msgstr ""

#: admin/cloud-search-admin-settings.php:585
msgid "Site ID"
msgstr ""

#: admin/cloud-search-admin-settings.php:580
msgid "In this section you can find a set of network settings to change default configurations. You can provide an alternative value for \"site_id\" and \"blog_id\". Modifying these options you can use different values from the default ones (eg: if you are using the same CloudSearch index from two different WordPress environment (localhost and staging), providing different values gives you the opportunity to use different keys for the same CloudSearch row without the risk of override your data)."
msgstr ""

#: admin/cloud-search-admin-settings.php:578
msgid "Network settings"
msgstr ""

#: admin/cloud-search-admin-settings.php:513
msgid "Enable if you want to search suggested items using only titles. If disabled, suggestion engine searches in all fields but may be slower."
msgstr ""

#: admin/cloud-search-admin-settings.php:510
msgid "Search only in titles?"
msgstr ""

#: cloud-search-indexer.php:233
msgid "Error uploading documents"
msgstr ""

#: admin/cloud-search-admin-settings.php:645
msgid "If you are using \"Multiple Post Thumbnails\" plugin, provide here the ID to retrieve the custom image."
msgstr ""

#: admin/cloud-search-admin-settings.php:641
msgid "Custom item image ID"
msgstr ""

#: admin/cloud-search-admin-help.php:201
msgid "This section is composed by fields that are used to set up generic configurations. The \"Custom field types prefix/suffix\" is very important if you want to filter the custom field types list in the \"Schema settings\". Provide a prefix or a suffix to retrieve a smaller set of custom fields instead all the registered fields (e.g. use \"cmb_,post_\", separated by comma, to select only fields that name starts by \"cmb_\" or \"post_\"). The \"Field values separator\" is used in text-array index fields for separate internal values (e.g. for category values use \"ID|NAME\", where \"|\" is the separator char). The field \"Item image size name\" gives you the opportunity to store in the CloudSearch index a custom image for every post. This value is not necessary to retrieve and show search query results, it's only used for extra features. Think at an external application that needs to read your CloudSearch data, providing a image size you can store in your index the featured image URL and the external application can read it without an extra lookup for the post image because it's already contained in your index. In the same way, if you are using the \"Multiple Post Thumbnails\" plugin, inserting in the field \"Custom item image ID\" the key to retrieve the custom \"Multiple Post Thumbnails\" image, you can also store this \"media\" type in the CloudSearch index."
msgstr ""

#: admin/cloud-search-admin-docs.php:629
msgid "PS: if a \"Custom item image ID\" is provided, the plugin will search the image using \"Multiple Post Thumbnails\" without reading the \"Item image size name\" field."
msgstr ""

#: admin/cloud-search-admin-docs.php:628
msgid "To solve this problem the plugin stores an extra text field with the name \"post_image\" and every time you sync a post this field is filled with the feature post image with the size that you have provided in the settings page. The size name is the value you have used in the \"add_image_size()\" function, or one of the reserved WordPress alias: thumb, thumbnail, medium, large, post-thumbnail. If not set, no post image is saved in the index. In the same way, if you are using the \"Multiple Post Thumbnails\" plugin, inserting in the field \"Custom item image ID\" the key to retrieve the custom \"Multiple Post Thumbnails\" image, you can also store this \"media\" type in the CloudSearch index."
msgstr ""

#: admin/cloud-search-admin-docs.php:625
msgid "More about item image size and custom item image ID fields"
msgstr ""

#: admin/cloud-search-admin-help.php:137
msgid "Mandatory fields are only: AWS region, search endpoint and domain name. If you provide an AWS Access key ID and an AWS Secret access key, the plugin uses these as credentials, otherwise it will try to use IAM roles. Using custom credentials gives you the opportunity to use different AWS keys for this service giving to these only a small set of permissions."
msgstr ""

#: admin/cloud-search-admin-settings.php:569
msgid "Go to link"
msgstr ""

#: admin/cloud-search-admin-settings.php:568
msgid "Do nothing"
msgstr ""

#: admin/cloud-search-admin-settings.php:565
msgid "Click behaviour"
msgstr ""

#: admin/cloud-search-admin-settings.php:560
msgid "Alphabetically reverse"
msgstr ""

#: admin/cloud-search-admin-settings.php:559
msgid "Alphabetically"
msgstr ""

#: admin/cloud-search-admin-settings.php:555
msgid "Suggested items order"
msgstr ""

#: admin/cloud-search-admin-settings.php:551
msgid "The maximum number of suggested items."
msgstr ""

#: admin/cloud-search-admin-settings.php:548
msgid "Number of results"
msgstr ""

#: admin/cloud-search-admin-settings.php:544
msgid "The minimum number of chars before the suggestions starts."
msgstr ""

#: admin/cloud-search-admin-settings.php:541
msgid "Chars trigger"
msgstr ""

#: admin/cloud-search-admin-settings.php:529
msgid "Styles (for focused row)"
msgstr ""

#: admin/cloud-search-admin-settings.php:523
#: admin/cloud-search-admin-settings.php:535
msgid "Background"
msgstr ""

#: admin/cloud-search-admin-settings.php:521
#: admin/cloud-search-admin-settings.php:533
msgid "Color"
msgstr ""

#: admin/cloud-search-admin-settings.php:519
#: admin/cloud-search-admin-settings.php:531
msgid "Font size"
msgstr ""

#: admin/cloud-search-admin-settings.php:517
msgid "Styles (for all rows)"
msgstr ""

#: admin/cloud-search-admin-settings.php:506
msgid "Any valid CSS selector will work. The default search box for WordPress is: input[name='s']"
msgstr ""

#: admin/cloud-search-admin-settings.php:503
msgid "Search field selector"
msgstr ""

#: admin/cloud-search-admin-settings.php:499
msgid "Enable search field suggestions (the \"Use jQuery\" flag is mandatory if you want to activate suggestions)."
msgstr ""

#: admin/cloud-search-admin-settings.php:496
msgid "Active"
msgstr ""

#: admin/cloud-search-admin-settings.php:491
msgid "In this section you can find a list of settings to set up the search suggestions. First of all you can activate the suggestions by turning on the \"Active\" flag. The other fields give you the opportunity to customize the suggestion output style (for generic and focused rows), the suggestion results order and max items, the click behavior when you click a suggested value, the jQuery selector for the search field and the typed chars before the suggestion starts. If active, after you have typed the number of your configured chars, the plugin makes a request to a CloudSearch API and gives you back the search results."
msgstr ""

#: admin/cloud-search-admin-help.php:197
msgid "Pay attention that, the \"Use jQuery\" flag is mandatory if you want to activate the search suggestions."
msgstr ""

#: admin/cloud-search-admin-help.php:196
msgid "This section is composed by fields that are used to set up the search suggestions configurations. First of all you can activate the suggestions by turning on the \"Active\" flag. The other fields give you the opportunity to customize the suggestion output style (for generic and focused rows), the suggestion results order and the max showed items, the click behavior when you click a suggested value, the jQuery selector for the search field and the typed chars before the suggestion starts. If active, after you have typed the number of your configured chars, the plugin makes a request to a CloudSearch API (note that API query searches only on the post title field in the current site, do not search in network) and gives you back the search results like a dropdown menu under the search field."
msgstr ""

#: admin/cloud-search-admin-help.php:195
#: admin/cloud-search-admin-settings.php:489
msgid "Suggestions settings"
msgstr ""

#: admin/cloud-search-admin-docs.php:585
msgid "Fields marked with (*) will be overridden with plugin settings (if configured)."
msgstr ""

#: admin/cloud-search-admin-docs.php:552
msgid "In order to customize the suggestions look & feel you can, if you need a simple customization, use the plugin settings configuration and change colors and font size, otherwise if you need a deeper customization you can modify the following CSS rules (simply changing values and appending the \"!important\" clause)."
msgstr ""

#: admin/cloud-search-admin-docs.php:551
msgid "Suggestions"
msgstr ""

#: admin/cloud-search-admin-docs.php:169
msgid "If you want to compile JS and CSS on your local machine, some Grunt tasks are available. First of all, install Grunt and dependencies using \"npm install\". The available tasks are:"
msgstr ""

#: admin/cloud-search-admin-docs.php:167
msgid "Development"
msgstr ""

#: admin/cloud-search-admin-settings.php:480
msgid "Insert a CSS class name, search results will be wrapped in a span with the provided class."
msgstr ""

#: admin/cloud-search-admin-settings.php:476
msgid "CSS class"
msgstr ""

#: admin/cloud-search-admin-settings.php:471
msgid "Provide a CSS inline style, style will be inserted in a span (eg: text-decoration:underline; color:#FF0000;)"
msgstr ""

#: admin/cloud-search-admin-settings.php:467
msgid "CSS style"
msgstr ""

#: admin/cloud-search-admin-settings.php:460
msgid "Background color"
msgstr ""

#: admin/cloud-search-admin-settings.php:456
#: admin/cloud-search-admin-settings.php:463
#: admin/cloud-search-admin-settings.php:525
#: admin/cloud-search-admin-settings.php:537
msgid "Use HTML color codes (#rgb or #rrggbb)."
msgstr ""

#: admin/cloud-search-admin-settings.php:453
msgid "Text color"
msgstr ""

#: admin/cloud-search-admin-settings.php:449
msgid "Highlight also in search result titles."
msgstr ""

#: admin/cloud-search-admin-settings.php:446
msgid "Highlight in titles?"
msgstr ""

#: admin/cloud-search-admin-settings.php:441
msgid "Underline"
msgstr ""

#: admin/cloud-search-admin-settings.php:440
msgid "Italic"
msgstr ""

#: admin/cloud-search-admin-settings.php:439
msgid "Strong"
msgstr ""

#: admin/cloud-search-admin-settings.php:438
msgid "None"
msgstr ""

#: admin/cloud-search-admin-settings.php:435
msgid "Style type"
msgstr ""

#: admin/cloud-search-admin-settings.php:430
msgid "In this section you can find a list of settings to highlight search results. You can choose a style type between: strong, italic and underline. Furthermore, you can choose if highlights titles and you can also customize the styles, giving a color (to the text and to the background), a CSS inline style and a CSS class to the highlighted word. Note that, by default, these settings are used in post content and post excerpt fields."
msgstr ""

#: admin/cloud-search-admin-settings.php:397
msgid "chars"
msgstr ""

#: admin/cloud-search-admin-settings.php:396
msgid "words"
msgstr ""

#: admin/cloud-search-admin-settings.php:391
msgid "Length of the text"
msgstr ""

#: admin/cloud-search-admin-settings.php:332
#: admin/cloud-search-admin-settings.php:363
msgid "Content"
msgstr ""

#: admin/cloud-search-admin-help.php:191
msgid "This section is composed by fields that are used to set up highlight configurations. The \"Style type\" field gives you the opportunity to choose an HTML style for every search hit, like \"strong\", \"italic\" and \"underline\". With the field \"Highlight in titles\" you can choose if you want to highlight search hits in titles. The \"Text color\" and \"Background color\" are very similar and are usefull if you want to apply an RGB color to every hit text or background. The last two fields, \"CSS style\" and \"CSS class\", are used to provide a CSS inline style and to insert a CSS class name. All the search hits will be wrapped in a span with the provided settings."
msgstr ""

#: admin/cloud-search-admin-help.php:190
#: admin/cloud-search-admin-settings.php:428
msgid "Highlighting settings"
msgstr ""

#: admin/cloud-search-admin-docs.php:359
msgid "Here a basic example for \"acs_api_search_full\" API:"
msgstr ""

#: admin/cloud-search-admin-docs.php:165
msgid "Highlights the given title according to plugin settings (highlight settings that you have configured in the settings page)."
msgstr ""

#: admin/cloud-search-admin-docs.php:162
msgid "Highlights the given text according to plugin settings (highlight settings that you have configured in the settings page)."
msgstr ""

#: admin/cloud-search-admin-docs.php:159
msgid "Truncates a text according to plugin settings (number of chars/words that you have configured in the settings page)."
msgstr ""

#: admin/cloud-search-admin-docs.php:156
msgid "Truncates a phrase according to given max words."
msgstr ""

#: admin/cloud-search-admin-docs.php:153
msgid "Truncates a phrase according to given max chars."
msgstr ""

#: admin/cloud-search-admin-docs.php:150
msgid "Here you can find a simple list of utility functions that you can use in your custom templates."
msgstr ""

#: admin/cloud-search-admin-docs.php:149
msgid "Some functions"
msgstr ""

#: admin/cloud-search-admin-docs.php:21
msgid "Utilities"
msgstr ""

#: admin/cloud-search-admin-docs.php:634
msgid "You can manipulate standard fields (such as post_title, post_content, etc) adding in your sub-theme a filter named \"cloud_search_#POST_TYPE#_fields\" by which you can change or adds all necessary fields according to your site data."
msgstr ""

#: admin/cloud-search-admin-docs.php:632
msgid "Manipulate standard fields"
msgstr ""

#. Author URI of the plugin
msgid "http://www.andrealandonio.it"
msgstr ""

#. Author of the plugin
msgid "Andrea Landonio"
msgstr ""

#. Description of the plugin
msgid "CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site."
msgstr ""

#. Plugin Name of the plugin
msgid "CloudSearch"
msgstr ""

#: templates/cloud-search-template-default.php:44
msgid "Sort by"
msgstr "Sorteret efter"

#: templates/cloud-search-template-default.php:40
msgid "Type"
msgstr "Type"

#: templates/cloud-search-template-default.php:28
msgid "You looked for: %s"
msgstr ""

#: templates/cloud-search-content-twentytwelve.php:164
msgid "This entry was posted on %3$s<span class=\"by-author\"> by %4$s</span>."
msgstr "Dette indlæg blev udgivet den %3$s<span class=\"by-author\"> af %4$s</span>."

#: templates/cloud-search-content-twentytwelve.php:161
msgid "This entry was posted in %1$s on %3$s<span class=\"by-author\"> by %4$s</span>."
msgstr "Dette indlæg blev udgivet i %1$s den %3$s<span class=\"by-author\"> af %4$s</span>."

#. Translators: 1 is category, 2 is tag, 3 is the date and 4 is the author's
#. name.
#: templates/cloud-search-content-twentytwelve.php:158
msgid "This entry was posted in %1$s and tagged %2$s on %3$s<span class=\"by-author\"> by %4$s</span>."
msgstr "Dette indlæg blev udgivet i %1$s og tagget %2$s den %3$s<span class=\"by-author\"> af %4$s</span>."

#: templates/cloud-search-content-twentytwelve.php:59
msgid "% Replies"
msgstr "% svar"

#: templates/cloud-search-content-twentytwelve.php:59
msgid "1 Reply"
msgstr "1 svar"

#: templates/cloud-search-content-twentytwelve.php:59
msgid "Leave a reply"
msgstr "Skriv et svar"

#: templates/cloud-search-content-twentytwelve.php:42
msgid "Featured post"
msgstr "Fremhævet indlæg"

#: templates/cloud-search-content-twentythirteen.php:156
msgid "View all % comments"
msgstr "Vis alle % kommentarer"

#: templates/cloud-search-content-twentythirteen.php:156
msgid "One comment so far"
msgstr "Én kommentar indtil videre"

#: templates/cloud-search-content-twentythirteen.php:120
#: templates/cloud-search-content-twentytwelve.php:151
msgid "View all posts by %s"
msgstr "Vis alle indlæg fra %s"

#. Translators: used between list items, there is a space after the comma.
#: templates/cloud-search-content-twentynineteen.php:150
#: templates/cloud-search-content-twentynineteen.php:163
#: templates/cloud-search-content-twentythirteen.php:70
#: templates/cloud-search-content-twentythirteen.php:78
#: templates/cloud-search-content-twentytwelve.php:92
#: templates/cloud-search-content-twentytwelve.php:98
#: templates/cloud-search-content-twentytwenty.php:163
msgid ", "
msgstr ", "

#: templates/cloud-search-content-twentythirteen.php:62
msgid "Permalink to %s"
msgstr "Permanent link til %s"

#. translators: %s: Name of current post
#: templates/cloud-search-content-twentysixteen.php:189
#: templates/cloud-search-content-twentysixteen.php:204
msgid "Edit<span class=\"screen-reader-text\"> \"%s\"</span>"
msgstr "Rediger <span class=\"screen-reader-text\"> \"%s\"</span>"

#: templates/cloud-search-content-twentyfourteen.php:111
msgid "% Comments"
msgstr "% kommentarer"

#: templates/cloud-search-content-twentyfourteen.php:111
msgid "1 Comment"
msgstr "En kommentar"

#: templates/cloud-search-content-twentyfourteen.php:111
#: templates/cloud-search-content-twentythirteen.php:156
msgid "Leave a comment"
msgstr "Skriv en kommentar"

#: templates/cloud-search-content-twentyfourteen.php:60
#: templates/cloud-search-content-twentythirteen.php:54
msgid "Sticky"
msgstr "Fastgjort"

#: templates/cloud-search-content-twentyfifteen.php:189
#: templates/cloud-search-content-twentyfifteen.php:194
#: templates/cloud-search-content-twentyfourteen.php:115
#: templates/cloud-search-content-twentythirteen.php:125
#: templates/cloud-search-content-twentytwelve.php:176
msgid "Edit"
msgstr "Ændre"

#: cloud-search.php:56
msgid "You don't have the permissions to perform this operation."
msgstr ""

#. translators: %s: post title
#: cloud-search-utils.php:937
#: templates/cloud-search-content-twentyfifteen.php:184
#: templates/cloud-search-content-twentyseventeen.php:188
#: templates/cloud-search-content-twentysixteen.php:181
msgid "Leave a comment<span class=\"screen-reader-text\"> on %s</span>"
msgstr "Skriv kommentar <span class=\"screen-reader-text\"> til %s</span>"

#: cloud-search-utils.php:926
#: templates/cloud-search-content-twentyfifteen.php:174
#: templates/cloud-search-content-twentyseventeen.php:126
#: templates/cloud-search-content-twentysixteen.php:172
msgctxt "Used before tag names."
msgid "Tags"
msgstr "Tags"

#: cloud-search-utils.php:915
#: templates/cloud-search-content-twentyfifteen.php:164
#: templates/cloud-search-content-twentyseventeen.php:116
#: templates/cloud-search-content-twentysixteen.php:162
msgctxt "Used before category names."
msgid "Categories"
msgstr "Kategorier"

#: cloud-search-utils.php:912 cloud-search-utils.php:923
#: templates/cloud-search-content-twentyfifteen.php:161
#: templates/cloud-search-content-twentyfifteen.php:171
#: templates/cloud-search-content-twentyfourteen.php:47
#: templates/cloud-search-content-twentyseventeen.php:113
#: templates/cloud-search-content-twentyseventeen.php:123
#: templates/cloud-search-content-twentysixteen.php:159
#: templates/cloud-search-content-twentysixteen.php:169
msgctxt "Used between list items, there is a space after the comma."
msgid ", "
msgstr ", "

#: cloud-search-utils.php:903
#: templates/cloud-search-content-twentyfifteen.php:153
#: templates/cloud-search-content-twentyseventeen.php:169
#: templates/cloud-search-content-twentysixteen.php:116
msgctxt "Used before post author name."
msgid "Author"
msgstr "Forfatter"

#: cloud-search-utils.php:862
#: templates/cloud-search-content-twentyfifteen.php:113
#: templates/cloud-search-content-twentysixteen.php:140
msgctxt "Used before publish date."
msgid "Posted on"
msgstr "Udgivet "

#: cloud-search-utils.php:836
#: templates/cloud-search-content-twentyfifteen.php:88
#: templates/cloud-search-content-twentynineteen.php:179
#: templates/cloud-search-content-twentyseventeen.php:179
#: templates/cloud-search-content-twentysixteen.php:150
msgctxt "Used before post format."
msgid "Format"
msgstr "Format"

#: cloud-search-utils.php:828
#: templates/cloud-search-content-twentyfifteen.php:81
msgid "Featured"
msgstr "Fasilitet"

#: cloud-search-utils.php:552
msgid "All"
msgstr "Alt"

#: cloud-search-hooks.php:39
msgid "Error managing post transitions for unpublished post"
msgstr ""

#: cloud-search-hooks.php:30
msgid "Error managing post transitions for published post"
msgstr ""

#: admin/cloud-search-admin.php:33 admin/cloud-search-admin.php:42
msgid "Documentation"
msgstr "Dokumentation"

#: actions/cloud-search-action-import.php:83
#: admin/cloud-search-admin-settings.php:743 cloud-search.php:89
msgid "Load more"
msgstr "Hent mere"

#: actions/cloud-search-action-import.php:81
#: admin/cloud-search-admin-settings.php:741 cloud-search.php:88
msgid "No results"
msgstr "Ingen resultater"

#: admin/cloud-search-admin-settings.php:685
msgid "Save"
msgstr "Spara"

#: admin/cloud-search-admin-settings.php:636
msgid "If you want to save an image for every indexed post provide the image size name (e.g. if you are using an \"add_image_size()\" custom format fill the name of the registered new image size). This value is not necessary to retrieve and display results, it's only used for extra features."
msgstr ""

#: admin/cloud-search-admin-settings.php:632
msgid "Item image size name"
msgstr ""

#: admin/cloud-search-admin-settings.php:627
msgid "Provide a field char to use as values separator (e.g. for category values use \"ID|NAME\", where \"|\" is the separator char)."
msgstr ""

#: admin/cloud-search-admin-settings.php:623
msgid "Field values separator"
msgstr ""

#: admin/cloud-search-admin-settings.php:614
msgid "Custom field types prefix/suffix"
msgstr ""

#: admin/cloud-search-admin-settings.php:609
msgid "In this section you can find a set of other settings to improve the plugin configuration. First of all you can provide a set (separated by \",\") of prefix or suffix that will be used to create the field types list you can find in the \"Schema settings\" section. Further than a set of default fields, with this option, you can tell the plugin which other fields you want to manage. Also, you can choose the separator to use for text-array values and you can provide a custom image size name to sync to the CloudSearch index (attention that this is not the image showed in the result box but it's only used to save in the schema the featured image URL, it's not mandatory, you can leave this field empty. This field is designed to be read by other applications)."
msgstr ""

#: admin/cloud-search-admin-settings.php:420
msgid "Default sort order"
msgstr "Standardsortering"

#: admin/cloud-search-admin-settings.php:416
msgid "Default sort field"
msgstr ""

#: admin/cloud-search-admin-settings.php:402
msgid "Search max items"
msgstr ""

#: admin/cloud-search-admin-settings.php:385
msgid "Load more message"
msgstr ""

#: admin/cloud-search-admin-settings.php:378
msgid "Provide a custom name for the no results content box (eg: content-none). The '##YOUR-VALUE##.php' template in your theme root folder will be used for no results box (eg: content-none.php). If the template is not in the theme root folder, add the folder path in the value field. If you set a custom box value it will be used instead of the default text message in case of no results."
msgstr ""

#: admin/cloud-search-admin-settings.php:373
msgid "No results message"
msgstr ""

#: admin/cloud-search-admin-settings.php:356
msgid "use a custom author format"
msgstr ""

#: admin/cloud-search-admin-settings.php:355
msgid "Author"
msgstr "Artikelansvarlig"

#: admin/cloud-search-admin-settings.php:350
msgid "use a custom date format (leave empty for default)"
msgstr ""

#: admin/cloud-search-admin-settings.php:349
msgid "Date"
msgstr "Date"

#: admin/cloud-search-admin-settings.php:344
msgid "use a custom image format (leave empty for default)"
msgstr ""

#: admin/cloud-search-admin-settings.php:343
msgid "Image"
msgstr "Billede"

#: admin/cloud-search-admin-settings.php:333
msgid "Excerpt"
msgstr "Uddrag"

#: admin/cloud-search-admin-settings.php:331
msgid "Comments link"
msgstr ""

#: admin/cloud-search-admin-settings.php:330
#: templates/cloud-search-content-twentytwenty.php:168
msgid "Tags"
msgstr "Emneord"

#: admin/cloud-search-admin-settings.php:329
#: templates/cloud-search-content-twentytwenty.php:50
msgid "Categories"
msgstr "Kategorier"

#: admin/cloud-search-admin-settings.php:328
msgid "Post formats"
msgstr "Indlægsformater"

#: admin/cloud-search-admin-settings.php:327
msgid "Sticky flag"
msgstr ""

#: admin/cloud-search-admin-settings.php:325
#: admin/cloud-search-admin-settings.php:361
msgid "Showed fields"
msgstr ""

#: admin/cloud-search-admin-settings.php:320
msgid "In this section you can customize your result pages choosing fields to display in every result item (further than the standard fields such as title, permalink, etc), default messages (for load more and no results), search max items and default filter values."
msgstr ""

#: admin/cloud-search-admin-settings.php:318
msgid "Results settings"
msgstr ""

#: admin/cloud-search-admin-settings.php:300
msgid "With this option you can choose if you want to show filter select boxes in your frontend search page. Using filters you can change the default results order and you can also apply a filter to the search query. Customizing your CSS you can easily change the filters layout."
msgstr ""

#: admin/cloud-search-admin-settings.php:296
msgid "Show filters"
msgstr ""

#: admin/cloud-search-admin-settings.php:289
msgid "Plugin needs to used jQuery to get search result asynchronously. If you don't want to use jQuery uncheck this flag to avoid plugin and jQuery scripts inclusion, but in this way you need to redefine a custom way to get search results. Look at the plugin REST endpoint to create your own search page."
msgstr ""

#: admin/cloud-search-admin-settings.php:284
msgid "Use jQuery"
msgstr ""

#: admin/cloud-search-admin-settings.php:278
msgid "If you choose to use the plugin search page it's highly recommended to use the jQuery support and the 'Plugin based' content box type."
msgstr ""

#: admin/cloud-search-admin-settings.php:277
#: admin/cloud-search-admin-settings.php:290
#: admin/cloud-search-admin-settings.php:345
#: admin/cloud-search-admin-settings.php:351
msgid "For more details click"
msgstr ""

#: admin/cloud-search-admin-settings.php:276
msgid "Selecting this value you choose to use the plugin search page instead the default WordPress search page, otherwise if you deselect this value you have to create your own search page."
msgstr ""

#: admin/cloud-search-admin-settings.php:271
msgid "Use plugin search page"
msgstr ""

#: admin/cloud-search-admin-settings.php:261
msgid "Content box type"
msgstr ""

#: admin/cloud-search-admin-settings.php:256
msgid "In this section you can choose the content box used to display search results and choose if you want to use the default plugin search page (or one created by your own), the jQuery support and if you want to show filter fields in the frontend search page."
msgstr ""

#: admin/cloud-search-admin-settings.php:191
msgid "With this option you can choose if you want to prevent (added by your hand) fields deletion when you create/update the index. Use this option if you have added to your CloudSearch schema some extra fields (by your hand) not using the plugin. Enabling \"prevent deletion flag\", when plugin run a indexing, do not manage all the \"external\" fields."
msgstr ""

#: admin/cloud-search-admin-settings.php:187
msgid "Prevent fields deletion"
msgstr ""

#: admin/cloud-search-admin-settings.php:141
msgid "Taxonomy types"
msgstr ""

#: admin/cloud-search-admin-settings.php:121
msgid "Field types"
msgstr ""

#: admin/cloud-search-admin-settings.php:101
msgid "Post types"
msgstr ""

#: admin/cloud-search-admin-settings.php:94
msgid "In this section you can choose the post, field and taxonomy types that you want to export to the index CloudSearch. Keep in mind that after every schema changes you have to update and re-index your CloudSearch index for use the \"modified\" schema configuration. Built-in taxonomies (category, tag and format) are added by default to the schema. Also you can find some other schema configurations."
msgstr ""

#: admin/cloud-search-admin-settings.php:84
msgid "Domain name"
msgstr ""

#: admin/cloud-search-admin-settings.php:80
msgid "Search endpoint"
msgstr ""

#: admin/cloud-search-admin-settings.php:50
msgid "AWS Region"
msgstr ""

#: admin/cloud-search-admin-settings.php:42
msgid "AWS Secret access key"
msgstr ""

#: admin/cloud-search-admin-settings.php:38
msgid "AWS Access key ID"
msgstr ""

#: admin/cloud-search-admin-settings.php:27
msgid "Note: There are only two required sections, the AWS and the index settings (only fields marked with \"*\" are mandatory). Without these configuration the plugin can not read/write to the AWS services. You can find a detailed support in the help pages. As mentioned before, other settings are not mandatory but is very important to set up them if you want a little bit of customization of your search page."
msgstr ""

#: admin/cloud-search-admin-settings.php:24
msgid "In this page you can manage all the plugin configurations. There are many sections, the AWS setting, the index settings, the schema setting, the frontpage setting, the result settings and other generic settings."
msgstr ""

#: admin/cloud-search-admin-settings.php:18 admin/cloud-search-admin.php:31
#: admin/cloud-search-admin.php:40
msgid "Settings"
msgstr "Instillinger"

#: admin/cloud-search-admin-manage.php:207
msgid "Are you sure to delete all documents?"
msgstr ""

#: admin/cloud-search-admin-manage.php:204
msgid "Delete all index documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:198
msgid "Delete document"
msgstr ""

#: admin/cloud-search-admin-manage.php:194
msgid "Are you sure to delete the document?"
msgstr ""

#: admin/cloud-search-admin-manage.php:192
msgid "use this action to perform a delete operation from your CloudSearch index. You can delete a single document (providing the CloudSearch ID) or the entire set of your site documents according with the post, field and taxonomy types configured in the settings section."
msgstr ""

#: admin/cloud-search-admin-manage.php:191
msgid "Delete documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:184
msgid "Are you sure to sync all documents?"
msgstr ""

#: admin/cloud-search-admin-manage.php:181
msgid "Sync all index documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:175
msgid "Sync document"
msgstr ""

#: admin/cloud-search-admin-manage.php:170
msgid "Are you sure to sync the document?"
msgstr ""

#: admin/cloud-search-admin-manage.php:170
#: admin/cloud-search-admin-manage.php:194
msgid "Invalid value"
msgstr ""

#: admin/cloud-search-admin-manage.php:167
msgid "Sync documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:142
msgid "Test connection"
msgstr "Test forbindelse"

#: admin/cloud-search-admin-manage.php:137
msgid "Run indexing"
msgstr ""

#: admin/cloud-search-admin-manage.php:135
msgid "Are you sure to run indexing?"
msgstr ""

#: admin/cloud-search-admin-manage.php:132
msgid "Create/update index"
msgstr ""

#: admin/cloud-search-admin-manage.php:130
msgid "Are you sure to create/update the index?"
msgstr ""

#: admin/cloud-search-admin-manage.php:128
msgid "use this action to create or update the index fields in CloudSearch (usually after every schema settings changes, e.g. if you add a new custom field type to your schema). After the create/update operation is completed, you need to run an indexing over your CloudSearch index. If your schema need an indexing you will be notified in the index status panel as explained before. The \"test connection\" action simply tells you if the index works correctly. "
msgstr ""

#: admin/cloud-search-admin-manage.php:127
msgid "Index management"
msgstr ""

#: admin/cloud-search-admin-manage.php:121
msgid "Actions"
msgstr "Aktion"

#: admin/cloud-search-admin-manage.php:106
msgid "Connection with CloudSearch index is not working or incomplete"
msgstr ""

#: admin/cloud-search-admin-manage.php:94
msgid "Operation in progress"
msgstr ""

#: admin/cloud-search-admin-manage.php:92
msgid "Current operation"
msgstr ""

#: admin/cloud-search-admin-manage.php:82
#: admin/cloud-search-admin-manage.php:105
msgid "Status"
msgstr "Status"

#: admin/cloud-search-admin-manage.php:72
msgid "Index fields"
msgstr ""

#: admin/cloud-search-admin-manage.php:62
msgid "Site documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:57
#: admin/cloud-search-admin-manage.php:67
#: admin/cloud-search-admin-manage.php:77
#: admin/cloud-search-admin-manage.php:87
msgid "Loading"
msgstr "Indlæser"

#: admin/cloud-search-admin-manage.php:53
#: admin/cloud-search-admin-manage.php:63
#: admin/cloud-search-admin-manage.php:73
#: admin/cloud-search-admin-manage.php:83
msgid "Reload"
msgstr "Genindlæs"

#: admin/cloud-search-admin-manage.php:52
msgid "Searchable documents"
msgstr ""

#: admin/cloud-search-admin-manage.php:43
msgid "Index status"
msgstr ""

#: admin/cloud-search-admin-manage.php:40
msgid "Note: There could be a time delay between index status page data and the real AWS data."
msgstr ""

#: admin/cloud-search-admin-manage.php:38
msgid "In this page you can view the index status, in particular, you can find how many documents you have in the index (divided by all searchable documents and documents of the current site), the defined index fields number and the index status (if running, if needs an indexing, if there is a pending operation). After the status section you have a list of actions that you can perform in the index."
msgstr ""

#: admin/cloud-search-admin-manage.php:27 admin/cloud-search-admin.php:30
#: admin/cloud-search-admin.php:39
msgid "Manage"
msgstr "Administrer"

#: admin/cloud-search-admin-help.php:311
msgid "Amazon CloudSearch pricing"
msgstr ""

#: admin/cloud-search-admin-help.php:310
msgid "What is Amazon CloudSearch"
msgstr ""

#: admin/cloud-search-admin-help.php:309
msgid "What is AWS"
msgstr ""

#: admin/cloud-search-admin-docs.php:288 admin/cloud-search-admin-help.php:307
msgid "Here you can find a list of utilities and references:"
msgstr ""

#: admin/cloud-search-admin-help.php:299
msgid "The plugin does not work with other languages plugins. However, there is a alternative and simple way to work with other languages. The best solution is to add custom fields containing language values into your index (e.g. titles, excerpts, contents and all the other textual fields) and a field that tells you if the post is translated. Then, customize the front page JavaScript adding an extra query filter (e.g. on \"is_translated\" field) at the default search key (see more details in the documentation page). Finally, you can manage in your custom content box what are the correct language fields to show (e.g. showing the english or the italian text depending on the language provided in the search query)."
msgstr ""

#: admin/cloud-search-admin-help.php:298
msgid "Works with multi language?"
msgstr ""

#: admin/cloud-search-admin-help.php:295
msgid "By default, search does not works on multisites. The basic search API looks only in the current site. If you want to search also in other sites you need to customize the page script for use the full search API version. This API searches in all sites and gives back to you the detailed results instead of a simple list of ID."
msgstr ""

#: admin/cloud-search-admin-help.php:294
msgid "Works on multisite?"
msgstr ""

#: admin/cloud-search-admin-help.php:288
msgid "The last 4 services are used only by the admin pages and you need a nonce token to get a response. The first one (as the second) is usable from everyone (do not need a nonce token) and gives you the ability to perform a query into CloudSearch. This service needs 3 parameters, a \"keyword\" with the searching word, a \"start\" and a \"size\" used for pagination and \"load more\" functionalities and gives back the list of objects representing the founding documents. You can get the API result in two formats: JSON and XML. The default one is JSON, but simply adding a \"format\" parameter in the API url you can switch the result output. Further information in the documentation section."
msgstr ""

#: admin/cloud-search-admin-help.php:278
msgid "The plugin use the built in AJAX WordPress functionality to retrieve asynchronous informations. You can call an API using the \"/wp-admin/admin-ajax.php\" page with one of the following \"action\":"
msgstr ""

#: admin/cloud-search-admin-help.php:261
msgid "As told before, the sync operation is thrown when a post/term is saved. In the \"Manage\" section you can start a sync or a delete task when you want. These operations are completely asynchronous and work like a batch scripts using chunks. When you start a sync (for deletion is the same process), the plugin registers a batch start, splits the documents to synchronize in subsets (chunk) to better manage asynchronous calls and at predetermined intervals sends data to the index until no chunks remains to be synchronized, then register a batch end. If you close the browser or you change the page, the plugin registers a batch pause and automatically resumes process when you come back to the \"Manage\" section again. In the \"Manage\" section you can see if a process is pending and how many documents are already synchronized. Pay attention that you cannot have more the one operation running at the same time, you have to wait an operation's end before launch a new one. The processes may take several minutes. Until processing completes, searches may return obsolete data. Anyway, it could be a little cache reading new CloudSearch data due to propagation time on AWS system."
msgstr ""

#: admin/cloud-search-admin-help.php:257
msgid "After installation and configuration, the plugin will use by default a built-in search template to provide CloudSearch results with no other customization needed, however there are different ways to customize your page. More informations about these features are detailed in the documentation page. The plugin provide an initial configuration that gives you a basic setting. If you want to alter this basic configurations, especially when using custom post types, post formats and custom fields/taxonomies, you can create your custom content boxes and change the content box type in the \"Frontpage settings\", you can create your search page and choose to not use the built-in search page using for example a different Javascript library (e.g. AngularJS or other frameworks instead of jQuery). These operations are suggested if you are using a custom theme and if you want to show more details or if you want a \"not-standard\" behavior in the result boxes."
msgstr ""

#: admin/cloud-search-admin-help.php:253
msgid "the index is in an invalid state. Need an indexing."
msgstr ""

#: admin/cloud-search-admin-help.php:253
msgid "Domain needs indexing (red)"
msgstr ""

#: admin/cloud-search-admin-help.php:252
msgid "the index is in a state that prevents new documents from being synced or some operation are in progress."
msgstr ""

#: admin/cloud-search-admin-help.php:252
msgid "Processing (yellow)"
msgstr ""

#: admin/cloud-search-admin-help.php:251
msgid "the index is active and running."
msgstr ""

#: admin/cloud-search-admin-help.php:251
msgid "Running (green)"
msgstr ""

#: admin/cloud-search-admin-help.php:249
msgid "The index status could be:"
msgstr ""

#: admin/cloud-search-admin-help.php:247
msgid "You can find the plugin dashboard under the a WordPress admin's menu with name of \"CloudSearch\". The plugin is composed by 4 main admin sections. The first two are the \"Help\" and the \"Documentation\" sections that are very useful to understand how plugin works and in which way you can customize the plugin behavior. In addition to these sections there are a \"Setting\" section that gives you the opportunity, after a initial setup, of customize the plugin. In the end, the \"Manage\" section is very important to check the index status, the searchable documents and above all for create, update, sync and delete data from your index."
msgstr ""

#: admin/cloud-search-admin-help.php:244
msgid "The front page uses the provided content box type to show a list of results. The page is completely asynchronous to speed up the page's rendition. On top of results you can find some filters. With these options you can filter results by post type and choose a different sort field (very useful to filter and expose relevant content). By default, sorting works with the value provided in the \"Results settings\" admin page. If you are using some custom post types, after you have stored them into the index, when you try a search they will be shown according to the \"Content box type\" value. Pay attention that, when using \"default\" or \"plugin\" content box, some fields of your custom types could be not properly shown due to \"not-standard\" usage. It's recommended to create different content boxes and work with the \"Formats and types based\" type. In this way you can separate boxes, one for the standard posts and one for every new custom post type (e.g. use \"content.php\" for standard posts and \"content-yourtype.php\" for new types)."
msgstr ""

#: admin/cloud-search-admin-help.php:240
msgid "the \"Lucene\" parser is used by default because this parser is very powerful for customized search query (using extra parameters) and for querying the schema"
msgstr ""

#: admin/cloud-search-admin-help.php:239
msgid "to increase information in the taxonomies instead of save only a ID or a name, the plugin use a \"separator\" syntax for append both the ID both the taxonomy name (e.g. \"789|My category\")"
msgstr ""

#: admin/cloud-search-admin-help.php:238
msgid "to maintain a CloudSearch pattern rule, every \"-\" character in a custom field/taxonomy slug is replaced with \"_\""
msgstr ""

#: admin/cloud-search-admin-help.php:212
msgid "the sets of standard fields automatically added to the schema:"
msgstr ""

#: admin/cloud-search-admin-help.php:211
msgid "a row key in the CloudSearch schema is defined with the pattern #site_id#_#blog_id#_#post_id#, in this way every row is completely unique and you can add external rows simply using a different #site_id#/#blog_id#, for example, your WordPress use a key like \"1_1_1234\", an external tool can use\"0_0_1234\", same post ID but for different environments. To avoid duplication on IDs a \"_term\" suffix is used for term items."
msgstr ""

#: admin/cloud-search-admin-help.php:209
msgid "In the following paragraph you can find a list of technical choices used for writing the plugin's core:"
msgstr ""

#: admin/cloud-search-admin-help.php:208
msgid "Plugin's behavior is very simple, after creating the schema on CloudSearch at every post transition event a sync of the modified document is throw through the AWS index to keep synchronized data between your WordPress database and CloudSearch schema (by default if a post is \"publish\" a insert/update is executed, otherwise, for drafts, delete, etc a delete is executed). Alternatively at the save post hook we have every time the possibility to force a sync/delete operation to a single post or for the entire database. Note that the plugin starts working only when the 'Amazon settings' and 'Index settings' fields are provided. In addition to the backend functionality the Plugin is integrated with the search engine of WordPress. If you provide a \"?s=\" value a search is performed using the plugin. The plugin catches the \"s\" parameter value, does a asynchronous call to an internal API and displays the search results according to the plugin settings explained above."
msgstr ""

#: admin/cloud-search-admin-help.php:200
#: admin/cloud-search-admin-settings.php:607
msgid "Other settings"
msgstr "Andre indstillinger"

#: admin/cloud-search-admin-help.php:186
msgid "Ascending"
msgstr "Stigende"

#: admin/cloud-search-admin-help.php:185
msgid "Descending"
msgstr "Aftagende"

#: admin/cloud-search-admin-help.php:183
msgid "The default sort order could be:"
msgstr ""

#: admin/cloud-search-admin-help.php:181
#: admin/cloud-search-admin-manage.php:154
msgid "ID"
msgstr "id"

#: admin/cloud-search-admin-help.php:180
msgid "Modified date"
msgstr ""

#: admin/cloud-search-admin-help.php:179
msgid "Publish date"
msgstr "Publiseringsdato"

#: admin/cloud-search-admin-help.php:178
#: admin/cloud-search-admin-settings.php:558
msgid "Relevance"
msgstr ""

#: admin/cloud-search-admin-help.php:176
msgid "The default sort field could be:"
msgstr ""

#: admin/cloud-search-admin-help.php:171
msgid "Username without link"
msgstr ""

#: admin/cloud-search-admin-help.php:170
msgid "Username with link"
msgstr ""

#: admin/cloud-search-admin-help.php:169
msgid "Full name without link"
msgstr ""

#: admin/cloud-search-admin-help.php:168
msgid "Full name with link"
msgstr ""

#: admin/cloud-search-admin-help.php:167
msgid "Display name without link"
msgstr ""

#: admin/cloud-search-admin-help.php:166
msgid "Display name with link"
msgstr ""

#: admin/cloud-search-admin-help.php:164
msgid "The author field formats could be:"
msgstr ""

#: admin/cloud-search-admin-help.php:162
msgid "This section is composed by fields that are used to customize the result items. These fields are used specially with the plugin content box type and the build-in jQuery scripts, if you use different solution not all of these option are used. Going deep in every single option. The \"Showed fields\" field is used to define which fields you what to show in the result item boxes (e.g. you can show the post content, the post excerpt, the post author, the post date, the featured image, etc). The \"No results message\" gives you the opportunity to set up a text if a search query gets no results, alternatively, you can provide a custom template for no results. The \"Load more message\" is similar to the \"No results message\", you can insert a text or, directly, the HTML. The field \"Length of the text\" give you the opportunity to limit the post content text (by choosing how many chars or words to display). The last 3 fields \"Search max items\", \"Default sort field\" and \"Default sort order\" are useful for set up the max page items, the default index field used for sort and the default sort order in the CloudSearch queries."
msgstr ""

#: admin/cloud-search-admin-help.php:161
msgid "Result settings"
msgstr ""

#: admin/cloud-search-admin-help.php:158
msgid "use the custom plugin \"content.php\" template located in plugin sources"
msgstr ""

#: admin/cloud-search-admin-help.php:158
msgid "Plugin based"
msgstr ""

#: admin/cloud-search-admin-help.php:157
msgid "use the default WordPress formats management with a named template prefix (eg: your_prefix-format_or_type_slug.php)"
msgstr ""

#: admin/cloud-search-admin-help.php:157
msgid "Formats and types based"
msgstr ""

#: admin/cloud-search-admin-help.php:156
msgid "use a named template from WordPress (eg: content-your_name.php)"
msgstr ""

#: admin/cloud-search-admin-help.php:156
msgid "Custom"
msgstr "Custom"

#: admin/cloud-search-admin-help.php:155
msgid "use the default \"content.php\" template from WordPress"
msgstr ""

#: admin/cloud-search-admin-help.php:155
msgid "Default"
msgstr "Default"

#: admin/cloud-search-admin-help.php:153
msgid "The section main field is the \"Content box type\". This field gives you the opportunity to set the search item box template choosing from:"
msgstr ""

#: admin/cloud-search-admin-help.php:151
msgid "This section is composed by fields that are used to customize the frontpage layout. The \"Use plugin search page\" gives you the opportunity to use the integrated search result page or to create one by your own. The \"Use jQuery\" field is useful if you do not want to use jQuery for frontend asynchronous call (for example, contacting the API). Disabling this field no jQuery scripts are loaded in page. Read the \"Documentation\" to understand how to customize your scripts and work with the API. The \"Show filters\" is used to choose if you want to display the filter dropdowns in the frontpage search page."
msgstr ""

#: admin/cloud-search-admin-help.php:150
#: admin/cloud-search-admin-settings.php:254
msgid "Frontpage settings"
msgstr "Forside-indstillinger"

#: admin/cloud-search-admin-help.php:148
msgid "#OBJ#<br /><br />"
msgstr ""

#: admin/cloud-search-admin-help.php:146
msgid "The section have a last field \"Prevent fields deletion\" that is useful if you change your index schema outside the plugin (by default the plugin deletes all the index fields not configured in the this section). For example, if you have added some index fields in the Amazon CloudSearch console and you do not want to lose your changes, enabling this field, when the plugin run an indexing do not remove fields not defined in the \"Schema settings\". If you have added fields to CloudSearch without using the plugin and, if by mistake, you have clicked the \"Create/update index\" button, don't worry! Before run an indexing you have to go in the AWS console and navigate to your \"Indexing options\" CloudSearch section (see image below). You can see some fields in a \"Pending Deletion\" status, you simply have to click recover to all the fields, then do an indexing to update the CloudSearch schema keeping your \"custom\" fields."
msgstr ""

#: admin/cloud-search-admin-help.php:144
msgid "This section is composed by 3 main fields that are used to select which custom types, fields and taxonomies you want to store into your CloudSearch index. For every list you have to select the rows that you want to save in the index. A set of default fields are already provided by the plugin, with this boxes you only add extra information. The post types and taxonomy types are composed automatically searching into your WordPress all registered custom types and custom taxonomies, instead, the field types need a manual setup. By default, retrieves all registered custom fields but you can limit the list values. Read the \"Other settings\" section to understand how to customize the field types list values."
msgstr ""

#: admin/cloud-search-admin-help.php:143
#: admin/cloud-search-admin-settings.php:92
msgid "Schema settings"
msgstr ""

#: admin/cloud-search-admin-help.php:141
msgid "In the \"Settings\" page there are more fields than the Amazon and Index settings. With the other fields you can highly customize the CloudSearch plugin. In the following paragraph we go deep into the other settings."
msgstr ""

#: admin/cloud-search-admin-help.php:134
msgid "Once you have finished to setup these two section you have to go the \"Manage\" section, press the \"Create/update index\" button and then run an indexing by pressing the relative button. After several minutes your index is ready to work and now you can start with an initial synchronization of all the documents."
msgstr ""

#: admin/cloud-search-admin-help.php:133
msgid "This section is composed by 2 fields that are used to communicate to a specific CloudSearch index schema. The fields are \"Search endpoint\" and \"Domain name\". All the information about these values are viewable in your Amazon CloudSearch domain dashboard (as you can read in the \"Setup Amazon AWS\" help section). For example, look at your index dashboard, you have the \"search-YOURNAME-wyg76gd7hdiagd87wqeguhgw72.eu-west-1.cloudsearch.amazonaws.com\" value that you use as \"Search endpoint\" and the \"YOURNAME\" value that you use as \"Domain name\"."
msgstr ""

#: admin/cloud-search-admin-help.php:132
#: admin/cloud-search-admin-settings.php:76
msgid "Index settings"
msgstr ""

#: admin/cloud-search-admin-help.php:117
msgid "This section is composed by 3 fields that are used to connect with the Amazon Web Services. The fields are \"AWS Access key ID\", \"AWS Secret access key\" and \"AWS Region\". All the information about these values are viewable in your Amazon account (as you can read in the \"Setup Amazon AWS\" help section)."
msgstr ""

#: admin/cloud-search-admin-help.php:116
#: admin/cloud-search-admin-settings.php:34
msgid "Amazon settings"
msgstr ""

#: admin/cloud-search-admin-help.php:113
msgid "After Amazon AWS account setup, you have to activate and setup the plugin. You have to go into the \"Settings\" page and fill the necessary data. This page is composed by different setting sections: an Amazon settings, a Index settings, a Schema settings, a Frontpage settings, a Result setting and a generic Other settings. For an initial setup you have only to set up the Amazon and Index settings. The other sections are not mandatory for the basic plugin configuration."
msgstr ""

#: admin/cloud-search-admin-help.php:108
msgid "Follow the set-up instructions explained for \"existing\" Amazon accounts. See above"
msgstr ""

#: admin/cloud-search-admin-help.php:107
msgid "Once verified, you can log in with your account username and password"
msgstr ""

#: admin/cloud-search-admin-help.php:106
msgid "There will be a phone identity verification"
msgstr ""

#: admin/cloud-search-admin-help.php:105
msgid "As mentioned before, AWS is not free, you will need to enter payment and billing informations"
msgstr ""

#: admin/cloud-search-admin-help.php:104
msgid "page and create a new account"
msgstr ""

#: admin/cloud-search-admin-help.php:104
msgid "Amazon Web Services"
msgstr ""

#: admin/cloud-search-admin-help.php:104
msgid "Visit the"
msgstr ""

#: admin/cloud-search-admin-help.php:102
msgid "If you do not have an Amazon Web Services account"
msgstr ""

#: admin/cloud-search-admin-help.php:99
msgid "When index is active save \"Search Endpoint\" URL (will be used during plugin configuration)"
msgstr ""

#: admin/cloud-search-admin-help.php:98
msgid "Initialization of your index (loading status)"
msgstr ""

#: admin/cloud-search-admin-help.php:97
msgid "Confirmation of creation"
msgstr ""

#: admin/cloud-search-admin-help.php:96
msgid "Review all the information and confirm index creation"
msgstr ""

#: admin/cloud-search-admin-help.php:95
msgid "Provide security policy (for demo, allow open access to all services)"
msgstr ""

#: admin/cloud-search-admin-help.php:94
msgid "Do not add index fields and go forward (the plugin will create fields)"
msgstr ""

#: admin/cloud-search-admin-help.php:93
msgid "Choose manual index configuration"
msgstr ""

#: admin/cloud-search-admin-help.php:92
msgid "Create new domain providing a name (use other values with defaults)"
msgstr ""

#: admin/cloud-search-admin-help.php:90
msgid "Proceed now with index creation following the steps explained below"
msgstr ""

#: admin/cloud-search-admin-help.php:89
msgid "Go to CloudSearch dashboard"
msgstr ""

#: admin/cloud-search-admin-help.php:88
msgid "Now you can copy keys to a text document (you will use during plugin activation) or you can create new ones"
msgstr ""

#: admin/cloud-search-admin-help.php:87
msgid "Click on the \"Account\" link in top right corner of the header, then click on \"Security Credentials\" to find your Access Key ID and your Secret Access key"
msgstr ""

#: admin/cloud-search-admin-help.php:86
msgid "Log in with your account username and password"
msgstr ""

#: admin/cloud-search-admin-help.php:84
msgid "If you have an Amazon Web Services account"
msgstr ""

#: admin/cloud-search-admin-help.php:83
msgid "To use CloudSearch plugin you will need an Amazon Web Services account configured. Please look the reference section and take some time to look over the AWS documentation. Now, continue reading to find how you can set-up AWS account."
msgstr ""

#: admin/cloud-search-admin-help.php:80
msgid "Before you can start using CloudSearch plugin, the Amazon account needs to be prepared and the plugin needs to be activated and configured."
msgstr ""

#: admin/cloud-search-admin-help.php:76
msgid "Upload the contents of \"cloud-search.zip\" into your plugins directory"
msgstr ""

#: admin/cloud-search-admin-help.php:75
msgid "Unzip the \"cloud-search.zip\" that you downloaded"
msgstr ""

#: admin/cloud-search-admin-help.php:73
msgid "Install manually"
msgstr ""

#: admin/cloud-search-admin-help.php:70
msgid "Click \"Choose File\", locate the \"cloud-search.zip\" file and click \"Install Now\""
msgstr ""

#: admin/cloud-search-admin-help.php:69
msgid "Click the \"Plugins\" menu and choose \"Add New\" from the top menu"
msgstr ""

#: admin/cloud-search-admin-help.php:66
msgid "Install by uploading the plugin through your WordPress dashboard"
msgstr ""

#: admin/cloud-search-admin-help.php:65
msgid "or after downloading \"CloudSearch\" you can:"
msgstr ""

#: admin/cloud-search-admin-help.php:63 admin/cloud-search-admin-help.php:71
msgid "You will receive a confirmation message when the plugin finishes installing"
msgstr ""

#: admin/cloud-search-admin-help.php:62
msgid "Select \"CloudSearch\" and click \"Install Now.\""
msgstr ""

#: admin/cloud-search-admin-help.php:61
msgid "Click the \"Plugins\" menu and enter \"CloudSearch\" into the search box"
msgstr ""

#: admin/cloud-search-admin-help.php:60 admin/cloud-search-admin-help.php:68
msgid "Log in to your WordPress admin dashboard"
msgstr ""

#: admin/cloud-search-admin-help.php:58
msgid "Install by searching the WordPress.org plugin repository"
msgstr ""

#: admin/cloud-search-admin-help.php:57
msgid "Like most WordPress plugins there are 3 ways to install a plugin."
msgstr ""

#: admin/cloud-search-admin-help.php:53
msgid "Uses Amazon's CloudSearch SaaS and runs on top of a WordPress installation with no additional servers, services, or hosting configuration needed"
msgstr ""

#: admin/cloud-search-admin-help.php:52
msgid "Integrates with your site's theme without the need for other customization. Provides optional features such as filtering and layout customization"
msgstr ""

#: admin/cloud-search-admin-help.php:51
msgid "Provides built-in methods for filtering post types and for sorting the results"
msgstr ""

#: admin/cloud-search-admin-help.php:50
msgid "Provides results based upon relevancy which provides better results than WordPress's standard text search"
msgstr ""

#: admin/cloud-search-admin-help.php:48
msgid "The plugin strengths:"
msgstr ""

#: admin/cloud-search-admin-help.php:45 admin/cloud-search-admin-help.php:274
#: admin/cloud-search-admin-settings.php:277
#: admin/cloud-search-admin-settings.php:290
#: admin/cloud-search-admin-settings.php:345
#: admin/cloud-search-admin-settings.php:351
msgid "here"
msgstr "her"

#: admin/cloud-search-admin-help.php:45
msgid "You can learn more about expected costs"
msgstr ""

#: admin/cloud-search-admin-help.php:44
msgid "CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site. The plugin is completely free. To use this plugin you'll need an Amazon Web Services account. Attention: Amazon CloudSearch is a paid service and will require a credit card. There are costs (based upon usage) associated with the Amazon CloudSearch service."
msgstr ""

#: admin/cloud-search-admin-docs.php:287 admin/cloud-search-admin-help.php:34
#: admin/cloud-search-admin-help.php:306
msgid "References"
msgstr ""

#: admin/cloud-search-admin-help.php:33 admin/cloud-search-admin-help.php:292
msgid "FAQ"
msgstr ""

#: admin/cloud-search-admin-help.php:32 admin/cloud-search-admin-help.php:277
msgid "API"
msgstr "API"

#: admin/cloud-search-admin-help.php:28 admin/cloud-search-admin-help.php:259
msgid "Sync operations"
msgstr ""

#: admin/cloud-search-admin-help.php:27 admin/cloud-search-admin-help.php:256
msgid "Customize your pages"
msgstr ""

#: admin/cloud-search-admin-help.php:26 admin/cloud-search-admin-help.php:246
msgid "WordPress admin section"
msgstr ""

#: admin/cloud-search-admin-help.php:25 admin/cloud-search-admin-help.php:243
msgid "Frontend results and filters"
msgstr ""

#: admin/cloud-search-admin-help.php:23 admin/cloud-search-admin-help.php:207
msgid "How plugin works"
msgstr ""

#: admin/cloud-search-admin-help.php:19 admin/cloud-search-admin-help.php:140
msgid "More about plugin settings"
msgstr ""

#: admin/cloud-search-admin-help.php:18 admin/cloud-search-admin-help.php:111
msgid "Setup CloudSearch plugin"
msgstr ""

#: admin/cloud-search-admin-help.php:17 admin/cloud-search-admin-help.php:82
msgid "Setup Amazon AWS"
msgstr ""

#: admin/cloud-search-admin-help.php:15 admin/cloud-search-admin-help.php:79
msgid "Configuration"
msgstr "Opsætning"

#: admin/cloud-search-admin-help.php:13 admin/cloud-search-admin-help.php:56
msgid "Installation"
msgstr "Installation"

#: admin/cloud-search-admin-help.php:12 admin/cloud-search-admin-help.php:42
msgid "About the plugin"
msgstr "Om pluginnet"

#: admin/cloud-search-admin-help.php:8 admin/cloud-search-admin.php:32
#: admin/cloud-search-admin.php:41
msgid "Help"
msgstr "Hjälp"

#: admin/cloud-search-admin-docs.php:627
msgid "The \"Item image size name\" and \"Custom item image ID\" fields are an extra feature used for storing in the index an extra field with a post image. To compose the result page the plugin retrieve a set of post IDs from the API, then using WordPress functions gets post information such as, title, permalink, image, etc. If you do not want to make an extra call to the WordPress functions or simply, you cannot do it, storing an extra field with the post featured image, lets you to show a result item without contacting WordPress anymore. This scenario could be very frequent in case of multisite with different sources that feed the CloudSearch index. You have no possibility to read the post image defined by a foreign environment."
msgstr ""

#: admin/cloud-search-admin-docs.php:612
msgid "The actual themes with an optimized template are:"
msgstr ""

#: admin/cloud-search-admin-docs.php:611
msgid "The plugin built-in template use a generic HTML optimized to fit in all the WordPress themes. If you are using a \"native\" WordPress theme, the plugin provide an optimized template for your theme. This choice is done by the plugin, if you choose the \"Plugin based\" content box type, when it's time to show the HTML results, the plugin gets your active theme, if it's a \"native\" theme use the optimized version for the theme, instead use the generic optimized HTML."
msgstr ""

#: admin/cloud-search-admin-docs.php:609
msgid "Plugin templates"
msgstr ""

#: admin/cloud-search-admin-docs.php:607
msgid "In the \"Setting\" section you have the opportunity to customize the \"no results\" message using a simple string, but you can also set an HTML template if you want to highly customize the \"no results\" message. If you are using a custom template none text messages will be displayed and if your search get no items your template will be displayed inside the results container."
msgstr ""

#: admin/cloud-search-admin-docs.php:606
msgid "Customize template for no results"
msgstr ""

#: admin/cloud-search-admin-docs.php:594
msgid "In the \"Setting\" section you have the opportunity to customize the \"load more\" message using a simple string, but you can also set an HTML snippet if you want to highly customize the \"loader\", for example with:"
msgstr ""

#: admin/cloud-search-admin-docs.php:593
msgid "Customize load more with HTML"
msgstr ""

#: admin/cloud-search-admin-docs.php:533
msgid "Changing this rules you can alter the search page item results layout. By default the plugin try to preserve the theme CSS rules, but overriding these rules you can modify every field in the container of a result item. You can modify the article container for post/term, the image, the header with the post title, the excerpt container and all the footer meta, such as the sticky flag, the post format, the post date/time, the author, the categories and terms list and the comment link boxes."
msgstr ""

#: admin/cloud-search-admin-docs.php:532
msgid "Front page item result rules"
msgstr ""

#: admin/cloud-search-admin-docs.php:519
msgid "Changing this rules you can alter the search page results section, you can modify the \"no results\" and the \"load more\" containers, the result items image to best fit it into your theme and the entire box container."
msgstr ""

#: admin/cloud-search-admin-docs.php:518
msgid "Front page results rules"
msgstr ""

#: admin/cloud-search-admin-docs.php:506
msgid "Changing this rules you can alter the search page filter section, you can change all about the filter dropdowns, the label style, the select input style and the entire box container."
msgstr ""

#: admin/cloud-search-admin-docs.php:505
msgid "Front page filters rules"
msgstr ""

#: admin/cloud-search-admin-docs.php:496
msgid "Changing this rules you can alter the search page header, especially, you can add custom rules for page title and subtitle. Usually the page title contains the phrase \"You looked for\" and the subtitle contains the result items counter."
msgstr ""

#: admin/cloud-search-admin-docs.php:495
msgid "Front page header rules"
msgstr ""

#: admin/cloud-search-admin-docs.php:492
msgid "Generally all the classes of the plugin start with the \"acs\" prefix. You can override the plugin CSS rules adding to your theme's stylesheet the following rules, changing the default values:"
msgstr ""

#: admin/cloud-search-admin-docs.php:456
msgid "Where \"code\" and \"message\" represent a feedback of the operation (e.g. \"ok\" or \"error\"), \"actions\" contains the actions performed (in the example, only the \"search_documents\" operation), \"data\" contains an object of specific informations. These informations are: \"items\", \"start\", \"found\", \"message\" and \"load_more\". The first one contains the result items in HTML format (provided by the content box selected in the admin settings page), the other fields could be used for manage the pagination, the no result message and the load more feature."
msgstr ""

#: admin/cloud-search-admin-docs.php:436
msgid "The API response looks like (JSON format):"
msgstr ""

#: admin/cloud-search-admin-docs.php:405
msgid "If you do not want to use jQuery or you need to change the script behavior, you can try to write your custom script code (with your preferred library or framework) and could be similar to:"
msgstr ""

#: admin/cloud-search-admin-docs.php:385
msgid "The built-in search page uses jQuery to initialize search engine. As you can see in the following code, the page provides some values to a ACS init function that manages the bootstrap and manages every search and pagination features. The \"init\" function parameters are: \"keyword\", \"start and \"size\" already explained in the \"acs_api_search\" API, \"type_field\", \"sort_field\" and \"sort_order\" that represent the filter element IDs and \"container_result_items\", \"container_ajax_loader\" and \"container_load_more\" that represent the element IDs where you want to put the result items, the page loader and the load more message."
msgstr ""

#: admin/cloud-search-admin-docs.php:384
msgid "How to write your custom script"
msgstr ""

#: admin/cloud-search-admin-docs.php:373
msgid "This service provides to you the index status. Especially if the index requires an indexing or if a sync/indexing operation is in progress."
msgstr ""

#: admin/cloud-search-admin-docs.php:370
msgid "This service provides to you the number of fields configured in the index."
msgstr ""

#: admin/cloud-search-admin-docs.php:367
msgid "This service provides to you the number of items in the site. In other words, the number of items that you can search using the search API."
msgstr ""

#: admin/cloud-search-admin-docs.php:364
msgid "This service provides to you the number of items in the index. In other words, the number of items that you can search using the search full API."
msgstr ""

#: admin/cloud-search-admin-docs.php:358
msgid "This service is similar to the previous explained, reads the same parameters but instead of search only in current site, search data in all sites and return a list of objects representing every indexed item. This service returns to you all the schema fields and should be used if your search page have to show data from different sources."
msgstr ""

#: admin/cloud-search-admin-docs.php:354
msgid "With this API you can query the index and get a list of IDs of the founded posts. This service read 4 parameters: \"keyword\" representing the search key (the only mandatory field), \"start\" and \"size\" representing the pagination values and \"filter_query\" to specify an extra filter query. Pay attention that this service works only with current site, if you need to search items in all the sites you have to use the next API."
msgstr ""

#: admin/cloud-search-admin-docs.php:351
msgid "The plugin provides to the user a set of APIs with which you can check the status of the index, verify the number of indexed documents and query the index to search for items. You can get the API result in two formats: JSON and XML. The default one is JSON, but simply adding a \"format\" parameter in the API url you can switch the result output. Below we analyze every single API."
msgstr ""

#: admin/cloud-search-admin-docs.php:342
msgid "In conclusion, if you need to search in a single site (probably a blog in a single site installation) you should use the standard API with the defaults plugin templates. If you need to search data in a network of multiple sites you should use full API customizing the scripts (for the API call) and the templates."
msgstr ""

#: admin/cloud-search-admin-docs.php:341
msgid "As already explained in the help page, the plugin uses site_id and blog_id to better works with multisite features. Every item is stored in the index with a unique key composed by the current site, the current blog and the post ID. In this way no duplicate can be saved in the index. By default all the queries performed with the standard \"acs_api_search\" API filter the result in the same site/blog, instead, using the \"acs_api_search_full\" API your results are searched in all the site/blog existing in the index. "
msgstr ""

#: admin/cloud-search-admin-docs.php:339
msgid "More about site and blog ID"
msgstr ""

#: admin/cloud-search-admin-docs.php:337
msgid "By default, the plugin searches your keyword in all the index fields, using frontend filters you can (for now) filter results by post type. If you want to filter your results on a specific field you have to use the syntax explained above and use a composed keyword, such as \"post_title:foo\" for search the word \"foo\" in the post title field. In addition, you can add other filters using a custom script and making an Ajax call passing the \"filter_query\" parameter with your desired filters, for example with a filter like \"post_format:video\" you can get only video posts. Keep in mind that the filter query is added with an AND condition to the default filter query."
msgstr ""

#: admin/cloud-search-admin-docs.php:336
msgid "Use filter queries"
msgstr ""

#: admin/cloud-search-admin-docs.php:332
msgid "An example of API request for searching for any word that starts with \"foo\" and ends with \"bar\" in the post title field could be (for demo we are limiting the results to 20 items):"
msgstr ""

#: admin/cloud-search-admin-docs.php:328
msgid "Note that performing range queries on numbers could be very heavy for the index."
msgstr ""

#: admin/cloud-search-admin-docs.php:327
msgid "Search for any values between the lower and upper bound specified by the Range Query in the post date field. Range Queries can be inclusive or exclusive of the upper and lower bounds. Sorting is done lexicographically."
msgstr ""

#: admin/cloud-search-admin-docs.php:322
msgid "Note that Lucene does not support using a * symbol as the first character of a search."
msgstr ""

#: admin/cloud-search-admin-docs.php:321
msgid "Search for any word that starts with \"foo\" and ends with \"bar\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:317
msgid "Search for any word that starts with \"foo\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:314
msgid "Search for word \"foo\" and not \"bar\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:311
msgid "Search for either the phrase \"foo bar\" in the post title field AND the phrase \"quick fox\" in the post content field, or the word \"fox\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:308
msgid "Search for phrase \"foo bar\" in the post title field AND the phrase \"quick fox\" in the post content field."
msgstr ""

#: admin/cloud-search-admin-docs.php:305
msgid "Search for phrase \"foo bar\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:302
msgid "Search for word \"foo\" in the post title field."
msgstr ""

#: admin/cloud-search-admin-docs.php:299
msgid "The plugin use the Lucene query parser as default parser for every CloudSearch search because is a very popular search engine library, with an active community and a host of real world implementations. Lucene has a custom query syntax for querying its indexes. Here are some query examples demonstrating the query syntax."
msgstr ""

#: admin/cloud-search-admin-docs.php:56 admin/cloud-search-admin-docs.php:182
#: admin/cloud-search-admin-docs.php:298 admin/cloud-search-admin-docs.php:350
#: admin/cloud-search-admin-docs.php:491
msgid "Overview"
msgstr "Oversigt"

#: admin/cloud-search-admin-docs.php:30
msgid "In this page you can read about the plugin documentation. In the docs you can find many detailed informations that explains you how to customize plugin CSS, API and much more."
msgstr ""

#: admin/cloud-search-admin-docs.php:27
msgid "Docs"
msgstr "Manualer"

#: admin/cloud-search-admin-docs.php:19
msgid "Querying the index"
msgstr ""

#: admin/cloud-search-admin-docs.php:18
msgid "Works with API"
msgstr ""

#: admin/cloud-search-admin-docs.php:17
msgid "CSS Styles"
msgstr "CSS stiler"

#: admin/cloud-search-admin-docs.php:16
msgid "General"
msgstr "Generelle indstillinger"