Changing system terminology

Hi Arlo,

It's in Administration > Translation > Terms.

Thanks Steven - I did see terms, but there are only 12 defined (token names/original terms) there. All relating to friends and groups. Presumably there must be more than that ... and if so, do you know where the exhaustive list of token names / original terms is. Presumably if I want to change the term 'blog' to 'newsfeed' for example, I need to know what the token name is, what the original term was, and then I just 'add new term' and then enter the old details, plus my new term, and bob's your uncle. 

Thanks Steven - I did see terms, but there are only 12 defined (token names/original terms) there. All relating to friends and groups. Presumably there must be more than that ... and if so, do you know where the exhaustive list of token names / original terms is. Presumably if I want to change the term 'blog' to 'newsfeed' for example, I need to know what the token name is, what the original term was, and then I just 'add new term' and then enter the old details, plus my new term, and bob's your uncle. 

I think you'll find the resources more exhaustive. All text strings shown to users are defined via these and customizable.

But where do I find a list of the tokens / original terms?

Each widget and theme defines all of its own language resources that it needs for all of its text. Those can be customized and/or translated both individually and en masse. I provided a bit more detail in my other reply to this thread. Please let me know if you have any questions!

Thanks Michael Monteleone yes I did see your reply, but understood you to mean that these are resource strings that are separate to the site terms. What I was really after is an exhaustive list of the default site terms (tokens and original terms). Once I have amended these, then I can look at which widgets have not consumed terms from there and adjust as necessary. 

The exhaustive default list is, in fact, only those 26 items. Site terms are unfortunately a somewhat legacy feature that are difficult to extend for multiple cultures and rarely consumed by the UI. While you may find changing them useful, I'd suggest you still investigate resource string exports/imports, as these phrases will likely appear more often than not directly within resource strings rather than as term references.

That said, here is the default set: