Skip to content

Norsk oversettelse av Subscribe to Comments Reloaded

av Odd Henriksen den 25. november 2010

Under arbeidet med å sette opp denne bloggen (som benytter WordPress), har jeg funnet noen nyttige “innstikk” – deriblant “Subscribe to Comments Reloaded” – som tillater brukere å abonnere på nye kommentarer til et innlegg. En ganske snedig sak, etter min mening.

Jeg har imidlertid ikke gjort det så lett for meg selv, fordi jeg valgte å gjøre denne bloggen flerspråklig. På grunn av det trenger jeg å ha mest mulig (helst alt) tilgjengelig både på engelsk og på norsk. Siden jeg ikke fant en eksisterende norsk oversettelse av Subscribe to Comments Reloaded, skrev jeg en selv.

Den norske oversettelsen (nb_NO) av Subscribe to Comments Reloaded er tilgjengelig her, dersom andre norske bloggere skulle ha interesse for den:

subscribe-reloaded-nb_NO

På grunn av måten innstikket fungerer på, ved at de fleste meldinger er konfigurerbare via WP-administrasjonssidene, og måten meldingene til syvende og sist blir “echoet” på, gjenstår det dog noen uløste hindre som blokkerer for at “Subscribe to Comments Reloaded” kan fungere optimalt på en flerspråklig blogg. Det kan se ut for at jeg blir nødt til å gjøre noen modifikasjoner i innstikkets kode for å løse denne problemstillingen, men det får jeg heller skrive mer om i et fremtidig innlegg, når jeg har litt bedre oversikt over det.

3 kommentarer
  1. Hi there, first of all thank you for writing these kind words about my plugin, I really appreciate it :) I started this as something I wanted to do for myself, since other similar plugins out there are not updated or not flexible enough for what I needed. I will include your translation in version 1.4, so if you want I can send you a preview of this new release which includes some new strings that you may want to translate. Just shoot me an email and I’ll send it to you.

    As for the multilanguage strings, I’d love to see what you have in mind to solve this issue. I’d like not to use multiple .po files, since most users don’t know how to edit them. But maybe I could add an option to specify if the plugin should use the strings in the database or those in the .po files. This way those who need a multilanguage environment, would be able to do so. Let’s discuss…

    Camu

    • Hi, and thanks for your comment.

      First of all, your development efforts with the plugin are much appreciated. You’re doing a great job!

      I understand well that you would prefer not to just use the gettext translation files, because that would make it harder to customize the strings for the average user.

      I am not entirely sure what would be the best approach in this case, but your suggestion of making it an option whether to use the default translation strings or the customized strings, is certainly one way.

      My immediate thought was to filter everything through a “__” or “_e” command, because that would
      1) Automatically make lookups against the active gettext translation
      2) Allow other plugins (such as qTranslate, which I am using) to process language tags. For example if I customized one of the strings to be [:en]English[:it]Italiano, qTranslate would cause the resulting output to be “English” if English was the active language or “Italiano” if Italian was the active language.

      Perhaps I’ll create a thread on your forum about this, where we can discuss it more thoroughly.

      Have a nice day!

  2. Johne604 permalenke

    Hi there! I know this is kind of off topic but I was wondering if you knew where I could locate a captcha plugin for my comment form? I’m using the same blog platform as yours and I’m having difficulty finding one? Thanks a lot!
    [random gibberish removed from end of post]

Legg igjen et svar

Merk: XHTML er tillatt. Din e-postadresse vil ikke bli publisert.

Varsle meg om nye kommentarer via e-post. Du kan også abonnere uten å legge inn en kommentar selv.