> > All of this seems familiar. I agree it should be the docs-writers who > must tell translators when to work on something, because only they > know the status of their documents. > > So far, I have been setting the translation status to "translations > not accepted" when a file is out of date or when I intend to work on > it. For example, the LilyPond-piano file has been this way for a while.[1] > > I like this because it's something writers can do, whereas I cannot > see how to remove files from the fedora-docs release. Also, with this > we can say that some files should not be translated and some should be > translated, rather than the whole Guide. > > What does this look like from the translators' perspective? Could it > work well? > Sure, I forgot about this one ;). Yep, having docs owner to setting the flag "currently not in translation" is great. I just have one concern: Some old guides are not deprecated, they are just not up to date or they are going to be updated soon. Sometimes you want to let translators know that they could translate but this won't be publish under the $LAST_RELEASE release, while some other times they should gently wait a little to work on the updated files. > > Christopher. > > [0] > https://fedora.transifex.net/projects/p/fedora-musicians-guide/resource/LilyPond-piano/ -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2 -- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
