Skip to content

How to translate "String Literals"? #48

Closed

Description

@iamsuperwen

As I working on #41, I encountered "7.1.1. Formatted String Literals".
Which would be the better translation of it, 字串實字 or 字串常數?

Activity

  1. Nienzu commented on Oct 14, 2018

    @Nienzu
    Contributor

    I think you can simply translate it into "字串".
    You can take the link for reference.

  2. yichung279 commented on Oct 16, 2018

    @yichung279
    Contributor

    c/cpp 社群似乎翻譯為「字串常數」
    https://www.ptt.cc/bbs/C_and_CPP/M.1463157729.A.28B.html

  3. adrianliaw commented on Oct 16, 2018

    @adrianliaw
    Collaborator

    I think the word "literal" is still important enough to include it in the translation, there's a difference between using and without using the vocabulary "literal", e.g. "some string" is a string literal, "some" + "string" is not a string literal but is a string. For "formatted string literals" here, the syntax can only be used when it's a string literal.

    I think "字串常數" is a plausible translation as its property of being a constant is documented inside Python's language reference, I've also seen people translating it to "字串文本", "字串常值", "字串字面值" etc. All the translations sound unnatural to me anyways, but I personally prefer "字串文本" just because "字串常數" can be confusing to those who come from programming languages that have constants.

    Anyhow, for each translated document that has the word "string literal" or "bytes literal" or something similar in it, we should always quote the original English word for the first appearance in that document, see tutorial/introduction.po for an example.

  4. iamsuperwen commented on Oct 16, 2018

    @iamsuperwen
    ContributorAuthor

    Thanks for the explanation.

    For each translated document that has the word "string literal" or "bytes literal" or something similar in it, we should always quote the original English word for the first appearance in that document.

    In sum, let's take "字串文本" as "string literal".

  5. added a commit that references this issue on Oct 17, 2018
  6. iamsuperwen commented on Oct 17, 2018

    @iamsuperwen
    ContributorAuthor

    Maybe just leave this open for discussion?

  7. locked and limited conversation to collaborators on Mar 2, 2023
  8. converted this issue into a discussion #402 on Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions