Changes between Initial Version and Version 1 of Ticket #30603, comment 5
- Timestamp:
- 12/07/2014 09:38:15 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30603, comment 5
initial v1 1 1 In the i18n tools it seems to me that there isn't a mechanism for handling inner-comment lines only beginning with a space and an asterisk: ' *'. That could be the issue with the comments not getting matched up. 2 2 3 FWIW, in my search I could only find five instances where translator comments were multi-line, four of them in TwentyFifteen and one of them in TwentyFourteen. I'd suggest lowercasing the 'T' for consistency and moving to single-l ongcomments as a precaution.3 FWIW, in my search I could only find five instances where translator comments were multi-line, four of them in TwentyFifteen and one of them in TwentyFourteen. I'd suggest lowercasing the 'T' for consistency and moving to single-line comments as a precaution. 4 4 5 5 Adversely, we could update the RegEx in `find_function_calls()` to handle multi-line comments. I'm thinking that would be a good later-addition at this juncture.