You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So what about file names that have a space in it, or perhaps have a semicolon? Those are valid file names and xgettext will happily process them and you will get something like this (I just renamed a file and then ran xgettext):
#: fdisk:big.c:234 fdisk:big.c:2942
I am not sure how common file names with semicolons are, but file names with spaces are not uncommon.
As far as I can tell partition() will not properly process this:
The only certainty that you have is that the part after the last : should be a number, so perhaps rewriting it to rpartition() would be the cleanest way.
The text was updated successfully, but these errors were encountered:
From #16 (comments)
So what about file names that have a space in it, or perhaps have a semicolon? Those are valid file names and
xgettext
will happily process them and you will get something like this (I just renamed a file and then ranxgettext
):I am not sure how common file names with semicolons are, but file names with spaces are not uncommon.
As far as I can tell
partition()
will not properly process this:The only certainty that you have is that the part after the last : should be a number, so perhaps rewriting it to rpartition() would be the cleanest way.
The text was updated successfully, but these errors were encountered: