DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13939>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13939 Translate task should have better key matching capabilities Summary: Translate task should have better key matching capabilities Product: Ant Version: 1.5.1 Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Translate task lets you pick a start token and an end token to delimit keys, but they must be single characters. This single character limitation makes it hard to pick a good delimiter character when you're running Translate against, say, an XSLT -- there just aren't many single characters left. Also, the Task actually has more internal conditions that are required before a string is considered a match. If I'm using # as my tokens, it corresponds to something like the regular expression: #[^\s=:#]# It might be nice to allow the user to specify a regular expression to determine what a string keys may look like, to reduce spurious matches. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
