Feature request: Case sensitive language string generation and other language string generation improvements #1007

New Issue

Open

opened 2023-09-15 21:52:38 +00:00 by Tom van der Laan · 0 comments

Tom van der Laan commented

2023-09-15 21:52:38 +00:00

Collaborator

Hi,

I think it would be nice to have case sensitive strings being generated. I don't think it does this right now, does it? I Find when my customer translates the project we always have some places where the word is not capitalised where you would expect it because the customer wanted it to display without capitalisation in different place. So you have to decide what to give priority.

It would be nice if the system would make a destinction between words being capitalised or not. So it would create two language strings for instance:

Training
training

Now results in COM_COMPONENT_TRAINING.

Would be nice if it would generate COM_COMPONENT_TRAINING & COM_COMPONENT_TRAINING_LC

i'm not entirely sure what it should do for language strings. Maybe we need some settings. For instance create unique strings per view for instance.

I find that sometimes i generate language strings in different places within my component and they have a different translation in dutch because the meaning is different in that specific place.

Wonder how you dealt with these things.

Kind regards,

Tom

Hi, I think it would be nice to have case sensitive strings being generated. I don't think it does this right now, does it? I Find when my customer translates the project we always have some places where the word is not capitalised where you would expect it because the customer wanted it to display without capitalisation in different place. So you have to decide what to give priority. It would be nice if the system would make a destinction between words being capitalised or not. So it would create two language strings for instance: Training training Now results in COM_COMPONENT_TRAINING. Would be nice if it would generate COM_COMPONENT_TRAINING & COM_COMPONENT_TRAINING_LC i'm not entirely sure what it should do for language strings. Maybe we need some settings. For instance create unique strings per view for instance. I find that sometimes i generate language strings in different places within my component and they have a different translation in dutch because the meaning is different in that specific place. Wonder how you dealt with these things. Kind regards, Tom