Help with options in phrases

[Matthew Hawley]

So I added an option to a phrase and this is what shows up.



Any suggestions? Thanks!
@Chris Deeming @Waindigo

 

[Jeremy]

Options aren't evaluated in phrases. You'd have to use a named variable {singular} and pass it in via the template:
{xen:phrase x, singular={yourOption}}

I'm on mobile so that syntax is probably not correct, but that's what you'll have to do.

 

[Matthew Hawley]

Options aren't evaluated in phrases. You'd have to use a named variable {singular} and pass it in via the template:
{xen:phrase x, singular={yourOption}}

I'm on mobile so that syntax is probably not correct, but that's what you'll have to do.

I know its correct. So I'd have to go into each template and add {xenhrase x, singular={yourOption}? Then can I add {singular} to the phrases?

 

[Jeremy]

Yes.

 

[Matthew Hawley]

Yes.

Wait so I have to do:

{xen:phrase x, singular={yourOption}

for EACH phrase?

 

[Jeremy]

Yes. If you want to define a {singular} variable for the phrase. I'd verify my syntax before you do a full on replace.

 

[Vincent]

Wait so I have to do:

{xen:phrase x, singular={yourOption}

for EACH phrase?

Yep, don't forget to close your first '{' though and to use these: '
I'd use a File Comparison tool if I were you

 

[Matthew Hawley]

Yes. If you want to define a {singular} variable for the phrase. If verify my syntax before you do a full on replace.

So can I add this to one template or do I have to add it to all templates?

 

[Jeremy]

Every time you use that phrase (where you have a variable defined), you must pass it a value.

 

[Matthew Hawley]

Ugh okay. 223 phrases to do. Time to get to work.

 

[Matthew Hawley]

Wait is this the correct format?

{xen:phrase adds_update_to_watched_resource, noncapitalsingular={nonCapitalizedRMSingularPhrases}

 

[Jeremy]

For one, you didn't close your opening curly brace. And no, it isn't.

This is (taken from XI blog):

{xen:phrase xi_blog_x_added_you_as_an_author_to_blog_entry_y,
    'name={xen:helper username, $user, 'subject'}',
    'title=<a href="{xen:link 'blog-entries', $content}" class="PopupItemLink">{$content.title}</a>'}

 

[Matthew Hawley]

For one, you didn't close your opening curly brace. And no, it isn't.

Then what is the correct format? Besides the curly brace.

 

[Jeremy]

{xen:phrase xi_blog_x_added_you_as_an_author_to_blog_entry_y,
    'name={xen:helper username, $user, 'subject'}',
    'title=<a href="{xen:link 'blog-entries', $content}" class="PopupItemLink">{$content.title}</a>'}

 

[Matthew Hawley]

{xen:phrase xi_blog_x_added_you_as_an_author_to_blog_entry_y,
    'name={xen:helper username, $user, 'subject'}',
    'title=<a href="{xen:link 'blog-entries', $content}" class="PopupItemLink">{$content.title}</a>'}

Could you post that as this?

{xen:phrase adds_update_to_watched_resource, noncapitalsingular={nonCapitalizedRMSingularPhrases}

 

[Jeremy]

You need to surround your variables (nocapitalsingular=x) with singular quotes. And you need to close your curly braces properly.

 

[Matthew Hawley]

{xen:phrase adds_update_to_watched_resource, noncapitalsingular={'nonCapitalizedRMSingularPhrases'}}

So like that?

 

[Jeremy]

No. Compare the format I posted to yours, you should be able to spot the differences.

 

[Matthew Hawley]

So this?

{xen:phrase adds_update_to_watched_resource, 'noncapitalsingular={nonCapitalizedRMSingularPhrases}'}

 

[Jeremy]

Test it and see. You may have problems with how you are passing the value to the variable in your phrase.