Package: po4a tag 1017742 fixed-upstream thanks Hello,
I just fixed the gettextization process, and I think it's now much better. The
version I introduced in last version was indeed really suboptimal.
Now, if I gettextize these two files (presented side by side):
```
# hello | # HELLO
|
## hello | ## SUBTITLE
|
hello | SAMPLE PARAGRAPH.
```
I get a pot file with a single msgid:
```
#, fuzzy, markdown-text, no-wrap
msgid "hello"
msgstr ""
"#-#-#-#-# file1:1 (type Title #) #-#-#-#-#\n"
"HELLO\n"
"#-#-#-#-# file1:3 (type: Title ##) #-#-#-#-#\n"
"SUBTITLE\n"
"#-#-#-#-# file1:5 (type: Plain text) #-#-#-#-#\n"
"SAMPLE PARAGRAPH."
```
I think it's much much better than the previous thing. Thanks again for
reporting the issue, I'm glad of that new version :)
Bye, Mt.
Le samedi 20 août 2022 à 10:43 +0200, Martin Quinson a écrit :
>
>
> ----- Le 19 Aoû 22, à 21:13, Helge Kreutzmann deb...@helgefjell.de a écrit :
>
> > Package: po4a
> > Version: 0.67-2
> > Severity: wishlist
> >
> > Since recently po4a-gettextize adds spaces at the end of strings
> > during gettextisation, if strings occure multiple times in the master
> > file (or translation).
> >
> > In production, multiple indentical strings in the original file are
> > only stored once in the po file (as they are translated the same).
> >
> > Therefore, translators need to review those strings carefully and
> > remove those entries from the po file, which have this final space
> > added. In this process they need to choose the most appropriate
> > translation to keep.
> >
> > Currently, this can be quite difficult, as the string can occur
> > multiple times and the trailing space(s) are difficult to spot in
> > large files. Also these trailing spaces are hard to get a good regular
> > expression for searching.
> >
> > Therefor I kindly ask you if you could mark those strings in addition
> > (!) with a suitable translator comment (e.g. "Potential duplicate
> > string, review and consolidate"). This would users allow to use msggrep(1)
> > with the option -C to filter them out for review.
> >
> > Thanks for considering.
>
> Your bug report makes me realize that the current behavior is perfectly
> broken. I was hopping for the next msgmerge to merge the alternative
> translations of the same msgid, but I realize that they will most probably be
> dropped in the process.
>
> Mmm. Let me think about it, I'll try to reimplement this thing so that the
> carful review that you describe becomes automatically done during the
> gettexization.
>
> Many thanks for reporting,
> Mt
--
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
signature.asc
Description: This is a digitally signed message part
