Please combine tier pricing messages into block sentences...

[hidonet]

Please combine tier pricing messages into block sentences...

[elenleonova]

Hi hidonet,
Would you mind to provide more information regarding your request, so we will be sure that we are on the same page with the suggested improvement?
Thanks

[hidonet]

Hi,
  Sentences about tier pricing in
  /app/design/frontend/base/default/template/catalog/product/view/tierprices.phtml
  is sliced to some parts. This makes translation difficult in some
  languages ( e.g. Turkish ).
  Example : line 105 "Buy %1$s for %2$s each"
  and line 189 <?php echo
  $this->__('save')?>&nbsp;<span class="percent
  tier-<?php echo $_index;?>"><?php echo
  $_price['savePercent']?></span>%
  Your Combined sentence is : Buy %1$s for %2$s each save 10%
  If you combine this into one sentence I can change order of
  variables. 
  Example : 
  "%1$ adet al, %2$ öde, %3$ karlı çık" 
  or 
  "Tanesine %2$ ödeyip, %1$ adet al, %3$ indirimli al"

[vpelipenko]

@hidonet, sorry for so late response, but I hope it will still useful for all. If we look at app\code\Magento\Catalog\view\base\templates\product\price\tier_prices.phtml we can see that phrase 'Buy %1 for %2 each and save %3' consists of 4 smaller phrases: 'Buy %1 for %2', 'each', 'and', 'save'.

First 2 can be easy combined, but the last two are the part of template, contain HTML formatting and depend on settings. It means that the last part of phrase 'and save %3' will appear on frontend if we enable showing detailed prices in backend settings. Does it make sense for you if we combine only first two phrases and leave the rest as is?

[hidonet]

I know this file and sentences. But in some languages ( for example in Turkish ) meaningfully combining sliced sentences is very difficult. Please add single sentence for every single state.

[vpelipenko]

Internal ticket has been created: MAGETWO-33393. We'll investigate the issue and come back with our solution.

[kokoc]

@hidonet Thank you for reporting the issue. The team has processed this ticket. Code changes have just been deployed in version 0.74.0-beta11. Could you please verify the issue?