Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add a method to change the context of a message #121

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

smnppKDAB
Copy link
Collaborator

No description provided.

@smnppKDAB smnppKDAB closed this Jul 22, 2024
@smnppKDAB smnppKDAB reopened this Jul 22, 2024
@smnppKDAB smnppKDAB force-pushed the sperret-setContext branch from 58c23f9 to 476d956 Compare July 22, 2024 15:34
@smnppKDAB smnppKDAB requested a review from dfaure-kdab July 22, 2024 15:40
@dfaure-kdab
Copy link
Member

Using the IDS_FOO which is stored in the "comment" to look up a specific message was my idea, but looking back at the merge request now I have to wonder if that's the right way to do this. When knut is used in another context than a MFC migration, the comment might not be a unique identifier for the message.... I think we need to pass context+comment+source (the message to be translated), to better identify the message that we want to move (same "key" as what tr() uses, AFAIK).

@smnppKDAB smnppKDAB force-pushed the sperret-setContext branch from 93bdc1d to c96398c Compare July 23, 2024 08:54
@smnppKDAB smnppKDAB force-pushed the sperret-setContext branch from 4d8d488 to 2c68a78 Compare July 23, 2024 10:23
@smnppKDAB smnppKDAB force-pushed the sperret-setContext branch from 34c0d3b to 91d1359 Compare July 23, 2024 11:15
@smnppKDAB smnppKDAB force-pushed the sperret-setContext branch from c61875a to b54b72a Compare July 23, 2024 11:19
@dfaure-kdab dfaure-kdab merged commit 3cbb216 into KDAB:main Jul 23, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants