On Thu, 21 Oct 2010, Graeme Geldenhuys wrote:
Op 2010-10-21 13:38, Michael Van Canneyt het geskryf:
* The default/standard file filter did not include all file types I
wanted - hence the reason they are included as customizable by the
end-user. The standard file filters are only imported once (on first
time use), thereafter the user can modify and customize them as they
see fit. The minor side effect is that those default file filter
are not translatable any more, but who really keeps changing there
IDE language back and forth - so I see this as a non-issue.
You should not take yourself as a reference for all users.
Each has his ways. I couldn't dream up the ways that some
users use my programs... Same here.
That said, I see no reason why you would not be able to fix this
problem. Just keep track of what are 'standard' filters and always
present the correct translation (i.e. the current text).
For user-added filters, obviously there is no translation.
If each filter in the IDE is uniquely named, you can keep track
of names that are 'standard' filters, and present them using the
original texts.
The same is true in all other parts of the IDE: file | new items are also
always uniquely named, and translatable. It's just a matter of correctly
implementing it. (I appreciate that of course the work must be done)
And this is where you and Vincent are wrong. The File Filters dialog allows
you to customize the filter name and the filter file mask.
You misunderstand. There is an INTERNAL name which you don't show to the
user. You are talking about the 'user displayed name'.
The internal name remains untouched.
Look at the way the 'File|new' items are done. It's the exact same
principle.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
