Hi guys,

please use this thread if you want to point out a label that is not correct or too long.

I am currently looking for a new label for "edit all records". It should be "edit multiple records" which, however, is too long. What do you native speakers think about "edit multiple" or "multi-edit mode"?

Regards
Leo

Hi Leo,

For me, either "multiple edit" or "multi-edit mode" works best.

regards,
David

Yeah ... I'm with David - I like the sound of these:
--> multi-edit
--> edit multiple
--> multiple edit

Here's a label thing I noticed yesterday - in the Member registration module > Activation jump to page >
replace "... after his account ..." with "... after their account ..."

Hi Ben,

my installation says "Please select the page to which a user will be redirected after his account has been activated". Is it wrong to say "a user" in this context? Should it be "users" instead?

If I only applied your change, it would be "Please select the page to which a user will be redirected after their account has been activated". I am sure you did not mean that, did you?

Regards
Leo

Hi Leo

You could say "Please select the page users are redirected to on their account activation"

How about just using "edit records"? or is this too ambiguous? Records as plural indicates more than one ie multi's

cheers

Mark

I believe it would be grammatically correct to say

"Please select the page users are directed to upon account activation."

This gets rid of the whole "their" issue altogether.

I like Mark's recommendation and I think Logan's brings it one step better.

I think Logan is best.

Though it is possible that some might interpret it wrongly if 'their' isn't there , that is they might think it indicates a generic page for redirection, but I doubt this would actually happen.

cheers

Mark

Most english copywriters (and people in PR communications) advise the use of active voice as grammatically preferred to passive voice, e.g.

Passive Voice:
Please select the page to which a user will be redirected after their account has been activated.

Active Voice:
After the system activates a user's account, it will redirect to the selected page.

I just noticed when I first login to the typolight admin area (2.6.7), main.php has some inconsistencies. It looks like "allows" is spelled "allowes" in 2 places:

Flash Content
This module allowes you to manage the dynamic content of a Flash movie.

Settings
This module allowes you to modify your local installation and to can change basic parameters like date format or character set.

All language files have been overworked for version 2.7 (see online demo).

leo:

All language files have been overworked for version 2.7 (see online demo).

I knew it.

BTW, will it be happen that any compatibility problem with translation files between 2.6.x and 2.7.x?
We can create trasnlation files for 2.7.0 and I heard that TYPOlight-Japanese-v16.zip and
TYPOlight-Japanese-v17.zip are already focused in 2.7.RC2. (I don't see contents of them yet.)

If there is no 2.6.x release after 2.6.7, it willl not be any problem. But if some reason (such as
security) might cause release 2.6.8, could translation files keep compatibility?

Best regards.

taca:

will it be happen that any compatibility problem with translation files between 2.6.x and 2.7.x?

No, you do not need to worry about that. Even though version 2.7 contains more labels than version 2.6, those additional labels are simply ignored if you install the language files under 2.6. Besides, if someone uses an older version of TYPOlight, he can download an older language package that has been published at the same time as the core version he is using (that is why the language download page shows the publication dates).

leo:

taca:

will it be happen that any compatibility problem with translation files between 2.6.x and 2.7.x?

No, you do not need to worry about that. Even though version 2.7 contains more labels than version 2.6, those additional labels are simply ignored if you install the language files under 2.6.

Yes, I already understood that. But existing labels are affected by changes for 2.7.

leo:

Besides, if someone uses an older version of TYPOlight, he can download an older language package that has been published at the same time as the core version he is using (that is why the language download page shows the publication dates).

Yes, she/he could. There are some inconvinience with current scheme.

• If we need TYPOlight version 2.6.8 for some reason (such as security), we don't have a good way to provide translation files for these reasons. For example, most of latest translation files for 2.6.7 lacks $GLOBALS['TL_LANG']['LNG']['ka'] in modules/backend/languages/??/languages.php, we have no way to provide translation file with added the line only for 2.6.7.
• Yes, user may select older version with publication dates, but she/he will be more happy translation files itself contain supporting TYPOlight's version.

These are my *very* small hope.

Of course, I don't wish more 2.6.x release.