[translations] A couple of untranslated strings in 5.x core

[Cog Rusty]

On 8/1/07, Cog Rusty <cog.rusty at gmail.com> wrote:
> On 8/1/07, Cog Rusty <cog.rusty at gmail.com> wrote:
> > On 8/1/07, Konstantin Käfer <kkaefer at gmail.com> wrote:
> > > The permission names are generated programatically [[ t("create ".
> > > $type ." content") ]] from the content type name. There is no good
> > > solution for this problem. You can translate these strings in your
> > > Drupal site manually, though.
> > >
> > > Konstantin
> >
> >
> > This is different. Not all node types have necessarily an "edit your
> > own" permission, so "edit your own" forum topics" is only defined in
> > the forum module and in no other module.
>
>
> Sorry, I replied too fast. There is "edit own " . $type in node module
> but it is not triggered except if a string for $type already exists in
> the database. And I was saying that it is possible to do that.
>

To be even clearer, I don't mind that "story" is not translated but at
least the surrounding "edit own" should be translatable.


>
> > > On 31.07.2007, at 23:18, Vasileios Lourdas wrote:
> > >
> > > > Hello,
> > > >
> > > > Following this thread, although it's a bit different issue this
> > > > time, there
> > > > are six strings that do not get translated after importing a
> > > > language gettext
> > > > file (e.g. Greek as in my case). These strings are:
> > > >
> > > > 1) create page content
> > > > 2) create story content
> > > > 3) edit own page content
> > > > 4) edit own story content
> > > > 5) edit page content
> > > > 6) edit story content
> > > >
> > > > which are role permissions and appear in the administration pages.
> > > > These
> > > > strings *do not* appear in the template files (.pot), however they
> > > > appear in
> > > > the Manage strings section of the Localization settings page (if
> > > > you search
> > > > using the right parameters).
> > > >
> > > > Since the Manage strings section provides me the ability to
> > > > translate them in
> > > > my language, I tried manually to insert those strings to a new .po
> > > > file and
> > > > translated them using my regular gettext file editor. Then I
> > > > imported the
> > > > merged file from all translations by all core modules and of course
> > > > this
> > > > procedure worked.
> > > >
> > > > The above make me wonder if there is a bug in Drupal 5.x core (I
> > > > haven't
> > > > checked 6-dev, though I will do so) that prevents potx from
> > > > extracting these
> > > > specific six strings to the template files, or there's something
> > > > else that
> > > > needs a bit of looking into.
> > > > --
> > > > # Vasileios Lourdas,
> > > > # Informatics Engineer, Thessaloniki (Greece)
> > > > # http://www.lourdas.name
> > > > _______________________________________________
> > > > translations mailing list
> > > > translations at drupal.org
> > > > http://lists.drupal.org/mailman/listinfo/translations
> > >
> > > Konstantin Käfer — http://kkaefer.com/
> > >
> > >
> > > _______________________________________________
> > > translations mailing list
> > > translations at drupal.org
> > > http://lists.drupal.org/mailman/listinfo/translations
> > >
> >
>