en_US.csv

Merchandiser,Merchandiser
Back,Back
Reset,Reset
"Save and Continue Edit","Save and Continue Edit"
Save,Save
"1 product","1 product"
"<%- count %> products","<%- count %> products"
"No products in the selected range.","No products in the selected range."
"Search Configuration","Search Configuration"
"Can be used only with catalog input type Text field, Dropdown, Multiple Select and Price.","Can be used only with catalog input type Text field, Dropdown, Multiple Select and Price."
"Display in autocomplete","Display in autocomplete"
"Facet coverage rate","Facet coverage rate"
"Ex: Brand facet will be displayed only if 90% of the product have a brand.","Ex: Brand facet will be displayed only if 90% of the product have a brand."
"Facet max. size","Facet max. size"
"Max number of values returned by a facet query.","Max number of values returned by a facet query."
"Facet sort order","Facet sort order"
"Search Weight","Search Weight"
"Used in spellcheck","Used in spellcheck"
First,First
Last,Last
"Sort products without value when sorting ASC","Sort products without value when sorting ASC"
"How the products which are missing values for this attribute should be treated when using it to sort.","How the products which are missing values for this attribute should be treated when using it to sort."
"Sort products without value when sorting DESC","Sort products without value when sorting DESC"
"Slider Display Configuration","Slider Display Configuration"
"Display pattern","Display pattern"
"A pattern like %s UNIT where %s is the value. Eg : $%s => $20 or %s € => 20 € or %s%% => 20%","A pattern like %s UNIT where %s is the value. Eg : $%s => $20 or %s € => 20 € or %s%% => 20%"
"Display Precision","Display Precision"
"The number of digits to use for precision when displaying.","The number of digits to use for precision when displaying."
"No exact results found for: <b>'%1'</b>. The displayed items are the closest matches.","No exact results found for: <b>'%1'</b>. The displayed items are the closest matches."
"No search specified.","No search specified."
"This search no longer exists.","This search no longer exists."
"Search results for ""%1""","Search results for ""%1"""
"Unable to save positions.","Unable to save positions."
Auto,Auto
"Always hidden","Always hidden"
"Always displayed","Always displayed"
"Result count","Result count"
"Admin sort","Admin sort"
Name,Name
Relevance,Relevance
"%1 and above","%1 and above"
"%1 - %2","%1 - %2"
"%1 is the only product matching your '%2' search.","%1 is the only product matching your '%2' search."
item,item
items,items
OK,OK
"Shop By","Shop By"
"Clear All","Clear All"
"Shopping Options","Shopping Options"
"Your product selection is empty.","Your product selection is empty."
"Automatic Sort","Automatic Sort"
"Manual Sort","Manual Sort"
"Show more","Show more"
"Minimum","Minimum"
"Maximum","Maximum"
Search,Search
"Refine search","Refine search"
"Clear search","Clear search"
"Your search returned no results.","Your search returned no results."
"Preview Only Mode","Preview Only Mode"
"Clear product positions","Clear product positions"
"Clear all products positions and blacklist status ?","Clear all products positions and blacklist status ?"
"In Stock","In Stock"
"Out Of Stock","Out Of Stock"
"Show less","Show less"
"No value matching the search <b>%s</b>.","No value matching the search <b>%s</b>."
"Search (%s)","Search (%s)"
"Product Autocomplete","Product Autocomplete"
"Max Size","Max Size"
"Maximum number of products to display in autocomplete results.","Maximum number of products to display in autocomplete results."
"Product Attributes Autocomplete","Product Attributes Autocomplete"
"Maximum number of product attributes to display in autocomplete results.","Maximum number of product attributes to display in autocomplete results."
"Category Autocomplete","Category Autocomplete"
"Maximum number of categories to display in autocomplete results.","Maximum number of categories to display in autocomplete results."
"Catalog Search","Catalog Search"
"Catalog Search Configuration","Catalog Search Configuration"
"Redirect to product page if only one result","Redirect to product page if only one result"
"If there is only one product matching a given search query, the user will be redirect to this product page.","If there is only one product matching a given search query, the user will be redirect to this product page."
"Use URL Rewrites for Category Filter in category navigation","Use URL Rewrites for Category Filter in category navigation"
"When set to yes, users are redirected (and all filters are reset) to the chosen category page when they use the category filter in layered navigation.","When set to yes, users are redirected (and all filters are reset) to the chosen category page when they use the category filter in layered navigation."
"Expanded facets","Expanded facets"
"Number of facets to display expanded by default.","Number of facets to display expanded by default."
"ElasticSuite Category Indexing","ElasticSuite Category Indexing"
"Reindex ElasticSuite catalog categories.","Reindex ElasticSuite catalog categories."
"Is Spellchecked","Is Spellchecked"
Yes,Yes
No,No
"Layered Navigation Filters","Layered Navigation Filters"
Attribute,Attribute
"Display Mode","Display Mode"
"Sort Order","Sort Order"
Pinned,Pinned
"Use Category Name in product search","Use Category Name in product search"
"Add New Optimizer","Add New Optimizer"
"All Store Views","All Store Views"
"Store View","Store View"
ID,ID
"Query Text","Query Text"
"No search result for the current search.","No search result for the current search."
"Clear all products positions and blacklist status ? All products will be reset to be visible and in 'Automatic Sort'.","Clear all products positions and blacklist status ? All products will be reset to be visible and in 'Automatic Sort'."
Products,Products
Categories,Categories
Attributes,Attributes
"No value matching the search <b>%1</b>.","No value matching the search <b>%1</b>."
"Logical OR (default)","Logical OR (default)"
"Logical AND","Logical AND"
"When several values are selected in a facet/filter, the default behavior is to combine them with a logical OR (""red"" OR ""blue""). But a logical AND can be handy for some attributes (""egg free"" AND ""gluten free"", ""waterproof AND lightweight AND warm"").","When several values are selected in a facet/filter, the default behavior is to combine them with a logical OR (""red"" OR ""blue"). But a logical AND can be handy for some attributes (""egg free"" AND ""gluten free"", ""waterproof AND lightweight AND warm"")."
"Facet internal logic","Facet internal logic"
"Category Name Weight","Category Name Weight"
"The search weight of category names when used in fulltext search.","The search weight of category names when used in fulltext search."
"Elasticsuite mapping has been updated real-time. However, your modifications might not be visible until the Catalogsearch Fulltext index is completely rebuilt.","Elasticsuite mapping has been updated real-time. However, your modifications might not be visible until the Catalogsearch Fulltext index is completely rebuilt."
"Elasticsuite mapping could not be updated real-time. Please wait for the complete reindexing of Catalogsearch Fulltext index.","Elasticsuite mapping could not be updated real-time. Please wait for the complete reindexing of Catalogsearch Fulltext index."
"Catalogsearch fulltext index has been invalidated.","Catalogsearch fulltext index has been invalidated."
"Enable adaptive slider","Enable adaptive slider"
"If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range.","If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range."
"Include zero or false values","Include zero or false values"
"If set to Yes, zero (integer or numeric attribute) or false (boolean attribute) values will be indexed in the search engine (default is No). Also applies to source model keys/values of Dropdown/Multiple Select attributes.","If set to Yes, zero (integer or numeric attribute) or false (boolean attribute) values will be indexed in the search engine (default is No). Also applies to source model keys/values of Dropdown/Multiple Select attributes."
"Display Category in Autocomplete","Display Category in Autocomplete"
"If the category can be displayed in autocomplete results.","If the category can be displayed in autocomplete results."
"Enable indexing child product SKU in dedicated subfield","Enable indexing child product SKU in dedicated subfield"
"If enabled, child products SKUs of composite products will be indexed in a separate field and the ""sku"" field will only contain the parent product sku.","If enabled, child products SKUs of composite products will be indexed in a separate field and the ""sku"" field will only contain the parent product sku."
"Enable indexing discount on child products","Enable indexing discount on child products"
"Enable this if your catalog contains configurable products that are having childrens with different prices that could have separated discounts.","Enable this if your catalog contains configurable products that are having childrens with different prices that could have separated discounts."
"Use this field for span queries","Use this field for span queries"
"Discard the field length for scoring","Discard the field length for scoring"
"Default : No. If set to Yes, the engine will try to match the current query string at the beginning of this string. Eg: when enabled on ""name"", if a customer search for ""red dress"", the engine will give an higher score to products having a name beginning by ""red dress"". This requires the Span Match Boost feature to be enabled.","Default : No. If set to Yes, the engine will try to match the current query string at the beginning of this string. Eg: when enabled on ""name"", if a customer search for ""red dress"", the engine will give an higher score to products having a name beginning by ""red dress"". This requires the Span Match Boost feature to be enabled."
"Default : No. By default, the score of a text match in a field will vary according to the field length. Eg: when searching for ""dress"", a product named ""red dress"" will have an higher score than a product named ""red dress with long sleeves"". You can set this to ""Yes"" to discard this behavior.","Default : No. By default, the score of a text match in a field will vary according to the field length. Eg: when searching for ""dress"", a product named ""red dress"" will have an higher score than a product named ""red dress with long sleeves"". You can set this to ""Yes"" to discard this behavior."
"Default Search Analyzer","Default Search Analyzer"
"Default : standard. The default analyzer for this field. Should be set to ""reference"" for SKU-like fields. You can check the %1 screen to view how these analyzers behave.","Default : standard. The default analyzer for this field. Should be set to ""reference"" for SKU-like fields. You can check the %1 screen to view how these analyzers behave."
"Text scoring algorithm","Text scoring algorithm"
"Default","Default"
"Boolean","Boolean"
"The text scoring algorithm (or ""similarity"") determines how the relevance score is computed for a field during search.<br/> Selecting ""Default"" will let your server apply the default scoring algorithm which takes into account every occurence of a search term in a field. Eg: a product with ""dress"" 3 times in its description should be scored higher than a product with ""dress"" only 1 time.<br/> You can opt for a ""Boolean"" scoring model that produces at most a score of 1 (before the ""Search weight"" is applied) for the whole field whatever the number of matches. Eg: the product with ""dress"" 3 times in its description would be scored the same as the product with ""dress"" only 1 time in its description.","The text scoring algorithm (or ""similarity"") determines how the relevance score is computed for a field during search.<br/> Selecting ""Default"" will let your server apply the default scoring algorithm which takes into account every occurence of a search term in a field. Eg: a product with ""dress"" 3 times in its description should be scored higher than a product with ""dress"" only 1 time.<br/> You can opt for a ""Boolean"" scoring model that produces at most a score of 1 (before the ""Search weight"" is applied) for the whole field whatever the number of matches. Eg: the product with ""dress"" 3 times in its description would be scored the same as the product with ""dress"" only 1 time in its description."
"<strong>Warning</strong>: a searchable attribute data is always copied to some searchable ""collector fields"" whose behavior will not be impacted by the change you do here.<br />So you might want to also look at the specific ""<strong>Text scoring algorithm for collector fields</strong>"" setting in the Stores Configuration section %1.","<strong>Warning</strong>: a searchable attribute data is always copied to some searchable ""collector fields"" whose behavior will not be impacted by the change you do here.<br />So you might want to also look at the specific ""<strong>Text scoring algorithm for collector fields</strong>"" setting in the Stores Configuration section %1."
"Elasticsuite &gt; Catalog Search &gt; Catalog Search Configuration","Elasticsuite &gt; Catalog Search &gt; Catalog Search Configuration"
"Text scoring algorithm for collector fields","Text scoring algorithm for collector fields"
"When performing a search, Elasticsuite will look both into fields related to searchable attributes with a search weight greater than 1 and into special collector fields (""search"", ""spelling"", etc.) where searchable attributes data can be copied to.<br />The text scoring algorithm (or ""similarity"") determines how the relevance score is computed for a field during search. While you can change it for every searchable attribute (in its advanced properties), you might want to also change it for those collector fields.<br />Selecting ""Default"" will let your server apply the default scoring algorithm which takes into account every occurence of a search term in a field. Eg: a product with ""dress"" 3 times in its ""search"" field should be scored higher than a product with ""dress"" only 1 time in its own ""search"" field.<br/> You can opt for a ""Boolean"" scoring model that produces at most a score of 1 for the whole field whatever the number of matches. Eg: the product with ""dress"" 3 times in its ""spelling"" field would be scored the same as the product with ""dress"" only 1 time in its own ""spelling"" field.","When performing a search, Elasticsuite will look both into fields related to searchable attributes with a search weight greater than 1 and into special collector fields (""search"", ""spelling"", etc.) where searchable attributes data can be copied to.<br />The text scoring algorithm (or ""similarity"") determines how the relevance score is computed for a field during search. While you can change it for every searchable attribute (in its advanced properties), you might want to also change it for those collector fields.<br />Selecting ""Default"" will let your server apply the default scoring algorithm which takes into account every occurence of a search term in a field. Eg: a product with ""dress"" 3 times in its ""search"" field should be scored higher than a product with ""dress"" only 1 time in its own ""search"" field.<br/> You can opt for a ""Boolean"" scoring model that produces at most a score of 1 for the whole field whatever the number of matches. Eg: the product with ""dress"" 3 times in its ""spelling"" field would be scored the same as the product with ""dress"" only 1 time in its own ""spelling"" field."
"Layered Navigation Configuration","Layered Navigation Configuration"
"Advanced Elasticsuite Configuration","Advanced Elasticsuite Configuration"
"Analysis Page","Analysis Page"
"Ignore manual positions of out of stock products","Ignore manual positions of out of stock products"
"If you show out of stock products in the frontend (through the ""Catalog / Inventory / Stock Options / Display Out of Stock Products"" stores configuration setting), switch this setting to Yes to make sure that a manually positionned product (in categories or in search queries) is no longer shown in the configured manual positions when it becomes out of stock.","If you show out of stock products in the frontend (through the ""Catalog / Inventory / Stock Options / Display Out of Stock Products"" stores configuration setting), switch this setting to Yes to make sure that a manually positionned product (in categories or in search queries) is no longer shown in the configured manual positions when it becomes out of stock."
"For showing products in categories, Elasticsuite relies on making sure all categories are ""anchor"" categories, that is displaying both their ""own"" products and the products associated with their subcategories.","For showing products in categories, Elasticsuite relies on making sure all categories are ""anchor"" categories, that is displaying both their ""own"" products and the products associated with their subcategories."
"The default value of the category attribute ""Is Anchor (is_anchor)"" is no longer set to 1 / Yes. This means all future categories created on the site will no longer automatically be ""anchor"" categories.","The default value of the category attribute ""Is Anchor (is_anchor)"" is no longer set to 1 / Yes. This means all future categories created on the site will no longer automatically be ""anchor"" categories."
"The category attribute ""Is Anchor (is_anchor)"" is no longer hidden on the Admin category edit page. This means the admin users can change categories to no longer being ""anchor"" categories.","The category attribute ""Is Anchor (is_anchor)"" is no longer hidden on the Admin category edit page. This means the admin users can change categories to no longer being ""anchor"" categories."
"This may cause some issues in the catalog navigation and search results pages.","This may cause some issues in the catalog navigation and search results pages."
"Some of your categories are not configured as ""anchor"" categories, this may cause some unexpected issues in the catalog navigation and search result pages.","Some of your categories are not configured as ""anchor"" categories, this may cause some unexpected issues in the catalog navigation and search result pages."
"This is the list of categories: %1","This is the list of categories: %1"
"Here are the first 5 categories: %1","Here are the first 5 categories: %1"
"There are %1 more categories in that situation.","There are %1 more categories in that situation."
"All categories are correctly configured as ""anchor"" categories.","All categories are correctly configured as ""anchor"" categories."
"Results","Results"
"Uses","Uses"
"Explicit URL rewrites support","Explicit URL rewrites support"
"How this works","How this works"
"By default, for performance reasons, Elasticsuite <strong>does not look into the URL Rewrites table at indexing time</strong> and rely instead on <strong>redirect URLs being automatically created by Magento when you change the URL key of a category</strong>. In the autocomplete, Elasticsuite thus reconstructs the URL of a category based on its url_key / url_path and the configured URL suffix which should always lead to a valid URL.<br />But if you often disable the automatic creation of those redirect URLs or if a user (or a third party module) frequently modifies the auto-generated URLs of categories, it can lead to categories being displayed in the autocomplete with an obsolete URL leading to a 404 page.<br />The setting below allows you to force Elasticsuite to look into the URL Rewrites table at indexing time to avoid that problem at the cost of a slight increase in indexing time.","By default, for performance reasons, Elasticsuite <strong>does not look into the URL Rewrites table at indexing time</strong> and rely instead on <strong>redirect URLs being automatically created by Magento when you change the URL key of a category</strong>. In the autocomplete, Elasticsuite thus reconstructs the URL of a category based on its url_key / url_path and the configured URL suffix which should always lead to a valid URL.<br />But if you often disable the automatic creation of those redirect URLs or if a user (or a third party module) frequently modifies the auto-generated URLs of categories, it can lead to categories being displayed in the autocomplete with an obsolete URL leading to a 404 page.<br />The setting below allows you to force Elasticsuite to look into the URL Rewrites table at indexing time to avoid that problem at the cost of a slight increase in indexing time."
"Enabled for categories","Enabled for categories"
"If set to ""Yes"", at indexing time, Elasticsuite will explicitely look into the URL Rewrites table (containing all the data visible from ""Marketing > SEO & Search > URL Rewrites"") to index the current URL of a category in order to display it in autocomplete results. If set to ""No"", Elasticsuite will use its legacy behavior of reconstructing the category URL from its indexed url_key / url_path and the configured URL suffix.","If set to ""Yes"", at indexing time, Elasticsuite will explicitely look into the URL Rewrites table (containing all the data visible from ""Marketing > SEO & Search > URL Rewrites"") to index the current URL of a category in order to display it in autocomplete results. If set to ""No"", Elasticsuite will use its legacy behavior of reconstructing the category URL from its indexed url_key / url_path and the configured URL suffix."