GNU gettext - Bugs: bug #61596, Support for Python f-strings
You are not allowed to post comments on this tracker with your current authentication level.
bug #61596: Support for Python f-strings
Submitter: | Ben <qtclyinh> | ||
Submitted: | Wed 01 Dec 2021 04:02:14 PM UTC | ||
Category: | Python | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Open |
Tue 07 Dec 2021 10:12:27 PM UTC, comment #4: |
Bruno Haible <haible>![]() ![]() |
Tue 07 Dec 2021 06:10:58 PM UTC, comment #3: I am afraid I did not express myself well: xgettext should not accept f-strings as arguments of () or gettext(), but should recognise () or gettext(), or whatever is defined, inside f-strings.
|
Ben <qtclyinh> |
Tue 07 Dec 2021 04:41:07 PM UTC, comment #2: Supporting this kind of strings in xgettext in the naïve way, i.e. where the string itself would appear as an msgid in the PO file, is not appropriate for the following reasons:
|
Bruno Haible <haible>![]() ![]() |
Wed 01 Dec 2021 04:04:48 PM UTC, comment #1: Sorry, the last example should read:
|
Ben <qtclyinh> |
Wed 01 Dec 2021 04:02:14 PM UTC, original submission:
Python 3.5 introduced f-strings, as specified in PEP 498 Literal String Interpolation:
|
Ben <qtclyinh> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Oh I see. You expressed yourself well; I misunderstood it.
That makes perfect sense.