Strange message construction; "{first_user} and {second_user} celebrate your ..."

Started by Oddbjørn Olsen on Sunday, December 5, 2010


Related Projects:

Showing all 15 posts
12/5/2010 at 11:56 AM{first_use...

There is another set of similar messages, with a more logical construction;{first_use...

Should the first set be removed?

Private User
12/5/2010 at 6:14 PM

From the look of it, the first phrase is for when {first_user}=YOU, but it's *really* awkward English. The verb should be in second person plural form, if this is relevant.

I would be more in favour of something like "You and {second_user} celebrate your anniversary...". But the {first_user} token becomes a link to your profile which would be lost by removing the token.

12/6/2010 at 7:38 AM

I actually see the use for this now.....what could be more embarrasing (& source to endless pillorying), than forgetting your own anniversary....good one !

I will assume you are right and re-write this to something along the lines of your suggestion (the you-user will probably be able to find their way onto Geni without the link...).

...unless we are talking about this one;

Private User
12/6/2010 at 4:54 PM

Computer-generated phrase fail. Either that, or love really *is* everlasting! ;)

Private User
12/6/2010 at 5:14 PM

Haha, awesome.

12/6/2010 at 10:45 PM

Spoiler - Warning; Humour attempt coming up;
"Due to the risk of senility at your age, Geni is taking the liberty of reminding you that {second_user} will be expecting some kind of attention on or about {date} relating to your <Anniversary text>. You have been warned!".

On a more serious note, here is my suggestion at the moment;

"{second_user} and you will celebrate your <anniversary text> {on_date}."

12/23/2010 at 6:47 AM

one correction to Oddbjørn Olsen's suggestion:
"{second_user} and you will celebrate your <anniversary text> on {date}."
this way we can use the translated date token without the english "on"

12/24/2010 at 4:12 AM

@Ya'acov ....if only....the {date} token is not known/available in this context so it just comes through as {date} (at least on the Norwegian version). Please confirm whether you have been able to make it work in another language.

12/24/2010 at 6:13 AM

Oddbjørn Olsen
I liked the idea to use {date}, but it didnt get well in hebrew

Private User
12/24/2010 at 11:50 AM

Can you give an example of where it doesn't work? I've done it well in Spanish at least.

12/24/2010 at 3:29 PM

It was taken from my homepage, I hope this works:

Ya'acov Glezer וRevital Glezer (Shimony) יחגגו את יום הנישואין ה-11(פלדה) שלך on December 30.

I know you can't read Hebrew but you can see that the date is in Latin letters
the token {on_date} needs better translation

Private User
12/24/2010 at 7:04 PM

@Yacov, but other than anniversaries, have you experienced this elsewhere?

12/24/2010 at 11:01 PM

- It seems that {on_date} is used only in anniversaries,
I've searched the for phrases containing it and found only this type of usage(199 anniversaries)
other phrases use "on {date}" and not "{on_date") as in those above.

Private User
12/25/2010 at 12:36 PM

Yeah, anniversary notifications need to be redone completely, allowing for [count:ord} ordinal case rules. No point in fixing a faulty to-be-defunct token.

12/25/2010 at 12:41 PM

The BIG question: WHEN????"

Showing all 15 posts

Create a free account or login to participate in this discussion