Being able to select non standard components easily

Re: Being able to select non standard components easily

על ידי David Mudrák בתאריך
מספר תגובות: 1
תמונה של Language pack maintainers

> i don't want to see anymore components i've already worked on (generating lot of results)

I see your point. However. Let us say we have this feature and so you are able to select all non-standard components. So you can easily select all 1349 components. Say 10% of them contains "URL" is some string, so you still end up with roughly 100+ selected components / strings. How will this new feature help you to not "see anymore components i've already worked on" ?

I admit this is kind of devil's advocate question, please don't get me wrong חיוך I just want to make sure that the feature requests are backed up with solid and thought-through use cases before we report them.

בתגובה ל: David Mudrák

Re: Being able to select non standard components easily

על ידי Séverin Terrier בתאריך

Hi David,

I completly understand that you only want to work for really useful things, and not implement everything everybody thinks about.

To be exact, with my actual problem (strings containing URL, in uppercase) : i've already reviewed 335 strings in french for standard components. If i select all components, i end with 723 strings. So, i've already done nearly half of the work. But, knowing that 171 strings aren't translated, i only have 723 - 335 - 171 = 217 strings to review (less than 40% of the work).

It's not too much work if i can find them easily ; if they're mixed with already reviewed one, it's much more work...

To write things short : it would ease the fact of working first on standard (priority), and then on non standard easily (when you've more time).

Séverin

PS : perhaps my use case is unusual ; i'm used to do things that are unusual to most people קריצה