Answers.Body: <p>If there’s a predetermined set of feature names, then you could translate them using <a href="https://docs.craftcms.com/v3/static-translations.html" rel="nofollow noreferrer">static message translations</a>.</p>
  
  <pre class="lang-twig prettyprint-override"><code>{% for row in entry.myTableField %}
    &lt;dt&gt;{{ row.featureName|t }}&lt;/dt&gt;
    &lt;dd&gt;{{ row.featureValue }}&lt;/dd&gt;
  {% endfor %}
  </code></pre>
  
  <p>If new products will always be introducing new feature names, then that might become impractical, as you’d be constantsly adding new values to your translation file.</p>
  
  <p>You could set up a custom translation message source + category in <code>config/app.php</code> that pulls translations in from a separate, translatable Table field on a Global Set, for instance, but that could be overkill.</p>
  
  <p>The other option is to use Verbb’s <a href="https://verbb.io/craft-plugins/super-table/features" rel="nofollow noreferrer">Super Table</a> plugin, which will let you mark certain fields as translatable.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T14:29:46.290Z
Answers.Text: Thanks for reply. Unfortunetly every product will have different options. So only viable solution is using that plugin, although im little anxious of basing my db content on external plugins. Do you plan on adding this feature to future versions of craft? Its not the first time i encoured this problem.
Answers.UserDisplayName: Ded Nolyxeux
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T15:20:33.910Z
Answers.Text: @DedNolyxeux Verbb is a super solid developer and Super Table is a popular plugin, so it’s a safe bet. If you want to stick with a native solution you could use a Matrix field.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T14:09:33.753Z
Answers.LastActivityDate: 2018-08-07T14:09:33.753Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>Lets say i have table field with product technical specification - two columns, one for feature name, one for feature value.</p>
  
  <p>Feature name (for example - "weight") needs to be translated across various languages. Feature value needs to always stay the same (for xample - "1kg").</p>
  
  <p>How can this be achieved?</p>
  
Tags: <localization><table-field>
Title: table field - make one culumn translatable, other common for all languages
ThreadText: # table field - make one culumn translatable, other common for all languages
  
  (Asked by: username_0 on 2018-08-07)
  
  Lets say i have table field with product technical specification - two columns, one for feature name, one for feature value.
  
  Feature name (for example - "weight") needs to be translated across various languages. Feature value needs to always stay the same (for xample - "1kg").
  
  How can this be achieved?
  
  **Tags:** localization, table-field
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-08-07. Score: 2
  
  If there’s a predetermined set of feature names, then you could translate them using [static message translations](https://docs.craftcms.com/v3/static-translations.html).
  
  ```twig
  {% for row in entry.myTableField %}
    <dt>{{ row.featureName|t }}</dt>
    <dd>{{ row.featureValue }}</dd>
  {% endfor %}
  
  ```
  
  If new products will always be introducing new feature names, then that might become impractical, as you’d be constantsly adding new values to your translation file.
  
  You could set up a custom translation message source + category in `config/app.php` that pulls translations in from a separate, translatable Table field on a Global Set, for instance, but that could be overkill.
  
  The other option is to use Verbb’s [Super Table](https://verbb.io/craft-plugins/super-table/features) plugin, which will let you mark certain fields as translatable.
  
  > **Comments:**
  > **username_0**: Thanks for reply. Unfortunetly every product will have different options. So only viable solution is using that plugin, although im little anxious of basing my db content on external plugins. Do you plan on adding this feature to future versions of craft? Its not the first time i encoured this problem.  
  > **username_1**: @username_0 Verbb is a super solid developer and Super Table is a popular plugin, so it’s a safe bet. If you want to stick with a native solution you could use a Matrix field.  
  
  ---
  
  