Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>gettext was designed to translate English text to other languages, and this is the way you should use it. Do not use it with keys. If you want keys, use some other technique such as an associative array.</p> <p>I have managed two large open-source projects (50 languages, 5000 translations), one using the key approach and one using the gettext approach - and I would never use the key approach again.</p> <p>The cons include propagating changes in English text to the other langauges. If you change</p> <pre><code>msg_no_food = "We had no food left, so we had to eat the cats" </code></pre> <p>to</p> <pre><code>msg_no_food = "We had no food left, so we had to eat the cat's" </code></pre> <p>The new text has a completely different meaning - so how do you ensure that other translations are invalidated and updated?</p> <p>You mentioned having long text that makes your scripts hard to read. The solution to this might be to put these in a separate script. For example, put this in the main code</p> <pre><code>print help_message('help_no_food') </code></pre> <p>and have a script that just provides help messages:</p> <pre><code>switch ($help_msg) { ... case 'help_no_food': return gettext("We had no food left, so we had to eat the cat's"); ... } </code></pre> <p>Another problem for gettext is when you have a full page to translate. Perhaps a brochure page on a website that contains lots of embedded images. If you allow lots of space for languages with long text (e.g. German), you will have lots of whitespace on languages with short text (e.g. Chinese). As a result, you might have different images/layout for each language.</p> <p>Since these tend to be few in number, it is often easier to implement these outside gettext completely. e.g.</p> <pre><code>brochure-view.en.php brochure-view.de.php brochure-view.zh.php </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCombining keys and full text when working with gettext and .po files
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USfisharebest
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGood point about invalidation. The alternative you're suggesting (with the `switch` example) adds an additional layer, which is basically what I would like from a translation format, that is to have a `1 - key/id` to keep views more concise and easily maintained, `2 - source` to make sure we have the exact source which is used for invalidation, and `3 - translation`. Do you know if any translation formats have that structure?
      singulars
      1. PO
      1. USMax
    2. COAs I said, I'd steer away from keys if at all possible. In my experience, it makes it harder to read/debug code - not easier. I only use them (indirectly via a switch) for help text, which tends to sit outside the rest of the code anyhow. PO format is great because it is widely used and understood by translators (as opposed to developers) and there are lots of tools to make their job easier.
      singulars
      1. PO
      1. USfisharebest
    3. COI fully understand what you're saying but there is one thing I can't get my head around: when you need to render the translation for an entire paragraph (e.g. company history): do you use the entire English paragraph in the `gettext` call? Sounds horrible to me, IMO it would make much more sense to do `gettext('company-history')`
      singulars
      1. PO
      1. USMax
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload