Wireshark mailing list archives
Qt translations when refactoring
From: Michael Mann via Wireshark-dev <wireshark-dev () wireshark org>
Date: Sat, 15 Jul 2017 17:09:45 -0400
I'm working on refactoring the Decode As dialog into using model/view functionality (https://code.wireshark.org/review/22625). The model appears to be "forced" to provide the names of the column headers that are part of the "table" in the Decode As dialog. Currently the names of the column headers are stored in the .ui file, but with the model the data of the .ui file isn't used. Is there any reason to keep the column info in the .ui file? Does it help provide context to translators? (Although my understanding is that the developers that have provided translation are familiar with Wireshark, unlike some general software translation services) If it's removed, do the translators have to do some rework even those the column names haven't changed? I'm just wrapping the existing English names with the tr() function. Any guidance on how to approach this (and future) refactors would be appreciated.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Qt translations when refactoring Michael Mann via Wireshark-dev (Jul 15)
- Re: Qt translations when refactoring Guy Harris (Jul 15)
- Re: Qt translations when refactoring Peter Wu (Jul 16)
- Re: Qt translations when refactoring Guy Harris (Jul 15)