Re: Q: Can you please assist me with translation?

[Mirsad Todorovac]

Hi, Paul, fellaz!

(Please npte that I've excluded address@hidden from this, as this
is purely technical issue, and I don't want to bother them with this. Also
I estimated that the fewer people involved, the lower synchronization
overhead will be ... :-)

On Fri, 12 Apr 2002, Paul Eggert wrote:

> > From: Mirsad Todorovac <address@hidden>
> > Date: Fri, 12 Apr 2002 15:23:47 +0200 (CEST)
> >
> > I'm Mirsad and I've got the job and honor ;-) to translate GNU tar to
> > Croatian, and perhaps other languages.
>
> Thanks.  In your translation, can you please make it clear which
> dialect you're using?  I assume it's Ijekavian, but that should be
> made clear in the translation file, in a comment in the header.  If
> the translation is also portable to other Stokavian dialects commonly
> used in Croatia (e.g., Ikavian) or to other non-Stokavian dialects
> (e.g., Cakavian, Kajkavian), that should also be noted.

OK. I see your point, and you've seen that we can create more problems
than we solve by involving this issue. From now on, please consider my
translation work to be into Stokavian/Ijekavian, which is sort of
lower-energy-state for me.

Croatian BORG has considerable fire-power, so it cannot be neglected, but
my work is for those who are worhty of it, not for the BORG.

Frankly, I would always encourage the thought that programs get translated
to dialects too (as Istrian Cakavian and other ...)

> > (Actually, I have already been given a blessing for Bosnian ...
>
> Which linguistic variant?  Again, this stuff should appear in the
> comments.

Personally I see no great problem with that, as long as it doen't create
me more problems that it solves. For completeness sake, I may add it, but
I guess I'll need further consulting to back me up.

> For completeness, the comments should appear in all translation files,
> not just those for GNU tar.

In case we agree to put them, but if only I do it of all hr translation
team, then what's the benefit?

> As we're both well aware, the issue of language variants in the former
> Yugoslavia is sensitive one.  It's important to make it clear exactly
> what the goal of the the translation is, to avoid ruffling feathers
> unnecessarily.
>
> Thanks.

I hope you will agree that presereving identity against assimilation is
sometimes more of an issue than mathematical linguistic distance (even if
we had an unquestionable way to define it) between languages.

> > I wondered can you assist me with some entries and program messages, that
> > I still have doubts of?
>
> Sure.

Great, so let's start some real work!

> PS.  Pardon my lack of accents, but bug-tar is an ASCII forum.

Taken into notice - please forgive me if I send 8-bit content to the list,
for it's a problem for me to strip accents each time -- is that OK?

(I'm positive that you will not see it the right way, but I'm needing your
assistance on the meaning of the original, not the translated text
anyway.)

So here we are (finally):

-----------------------------------------------------------

1.

# FIXME -- find `padež' here from source
#: src/create.c:151
msgid "Generating negative octal headers"
msgstr "Generiram negativna oktalna zaglavlja"

        Here I haven't realized in which person and declination
        is this "Generating negative octal headers" said;
        is it "Now I am generating octal headers" or
        "While generating octal headers" or something else?

2.

# FIXME -- non-header dubious -- clean against source! -- TM
#: src/delete.c:258
msgid "Deleting non-header from archive"
msgstr "Brišem non-header iz arhive"

        "Deleting non-header from archive" -- what is program really
        doing here?

3.

# FIXME -- clarify this against source -- TM -- didn't help
#: src/extract.c:1216
msgid "Visible long name error"
msgstr "Vidljiva pogreška s dugim imenom"

        What does this mean exactly?

4.

 FIXME -- obsolescent -- TM
#: src/list.c:632
msgid "Archive contains obsolescent base-64 headers"
msgstr "Arhiva sadrži zastarjela base-64 zaglavlja"

        What are exactly these base-64 and base-256 headers?

5.

# FIXME??
#: src/list.c:645
#, c-format
msgid "Archive signed base-64 string %s is out of %s range"
msgstr "Base-64 potpis %s arhive je izvan %s opsega"

        Can you please explain further this?
        Is this a sort of signature of the content or what?

6.

# FIXME -- clarify against source -- TM
#: src/list.c:1108
#, c-format
msgid "--Continued at byte %s--\n"
msgstr "--Nastavljeno sa bajtom %s--\n"

        What is continued here? I suppose archive, but if I'm
        not sure about the original, then I can be even less
        sure about the translation, wouldn't you agree.

7.

# FIXME -- 'mangled filenames'???
#: src/list.c:1112
msgid "--Mangled file names--\n"
msgstr "--Manglirana imena datoteka--\n"

        Can you explain further mangled filenames, their
        use in GNU tar (which is off course rather sophisticated
        software)?

8.

# FIXME -- now this is supposed to be funny
#: src/rmt.c:560
#, c-format
msgid "rmtd: Garbage command %c\n"
msgstr "rmtd: %c je smeće of naredbe\n"

        What types of commands are considered 'garbage'
        and when this occurs?

9. Can you please explain the use of 'volume number'
   term?

10. "  -i, --ignore-zeros             ignore zeroed blocks in archive
(means EOF)\n"

        I've read about this in manual, but this still looks rather
cryptic

--------------------------------------------------------------------

You will realize that I consider GNU `tar' an essential piece of software,
important for professionals and for other users, and that I want to do
this task the best possible way.

Thanks for help in forward,
Mirsad


-- 
This message has been made up using recycled ideas and language constructs.
No tree has been cut nor animal harmed in process of making it.

Visit http://www.thehungersite.com/, save one CHILD from DYING!!!