GerardM | 1 May 11:03
Picon

Re: Re[2]: be-tarask

Hoi,
There is the official orthography which is "be". This is also the default for the be code. It is the "be-tarask" that has to identify itself as such.
Thanks,
     Gerard

On 5/1/07, Jaska Zedlik <sub <at> zedlik.com> wrote:
Lars Aronsson wrote:

LA> If I understand this right, there was a book by Mr. Taraskievich
LA> in 1918, published in its 5th edition in 1929, then an official
LA> government reform in 1933 and one more in 1959.  Then in 2005 a
LA> new book that connects back to 1929.  We now have 5 different
LA> years that each could identify a slightly different version of the
LA> language, but these five can be grouped into two major branches:
LA> the 1933-1959 version that is today the official version in the
LA> republic of Belarus and the 1918-1929-2005 version now to be
LA> registered as "be-tarask".

Yes, you are right. But really there are/were not only 5 versions
but the majority of them can be put to one of these 2 branches.

>>From a philosophical standpoint, you need names for things only to
LA> tell them apart.  If there was no difference between apples and
LA> pears, we could just call it "fruit" and that would be it.  It
LA> follows that if there is a difference and you need a word for
LA> "apples", then you also need a word for "pears".

Probably. But in Belarusian if somebody eats apples, he or she doesn't
eat pears and vice versa. This means if somebody uses Taraskievica,
he usually don't want to know how to tag Narkamauka, and if somebody
writes in Narkamauka he usualy don't want to deal with Taraskievica.

LA> It is peculiar (to me) already that "be-tarask" is registered
LA> without also registering a subtag for the other, official version
LA> of Belarusian.  Suppose I start up my word processor and activate
LA> the spelling correction.  Which dictionary do I want to use?
LA> Be-tarask or the other one that doesn't have a subtag?  Is that to
LA> be called "be" without the subtag?  The only similar case I know
LA> is de-1901 and de-1996, where both subtags were registered at the
LA> same time.

Yes, this is still a problem, but the first step to solve it was made
by registering be-tarask. Now it is the turn of Narkamauka users to
find an appropriate title for Narkamauka subtag if they need a subtag.
But for now be-tarask means all the Taraskievica variants and
what means "be" depends only on the autor who tagged the data. Until a
subtag for Narkamauka doesn't exist, it is impossible to say that "be"
without a subtag stands for some specific variant of the language.

LA> The above post from Ihar is the first time I see that the 2005
LA> version would be "VERY different" from the 1929 version.

I don't really think, that they are "VERY different". The difference
between them are mainly in non-specified then rules and in the
orthography of foreign words, because it was not relevant in 1929. And
this difference is certainly less than between 2005 version and the
official orthography.

LA> Does
LA> that mean somebody will need to register a new subtag for the 1929
LA> version, to tell it apart from the 2005 version?

Initially be-tarask was intended to tag all sorts of Taraskievaca. But
as we need one concrete book to specify the set of rules for it,
certainly was chosen the latest as the most full and the most modern.
I don't think that somebody will create a spellchecker for 1929
orthography and check the books written then. This version is not in
use now, but this data if ever can also be tagged as "be-tarask".
Certainly for a non-user it can be quite hazy, but to compare it to
German, only de-1901 and de-1996 exist and nobody wants a subtag to
spellcheck some Goethe poems in original because this looks a bit
crazy. In Belarusian it is sometuing like this.

LA> Are there
LA> different newspapers printed in these two sub-sub-versions of
LA> Belarusian?

No, all the newspapers and magazines printed in Taraskievica
during the last 15-20 years are printed in 2005 version (or in the
variant which is very similar to it).

LA>   In the light of this, was it perhaps a mistake to use
LA> the name of the 1918-1929 author, Mr. Taraskievich, as the basis
LA> for the subtag for the 2005 version of the language?

Probably therefore 2005 version was called "Belarusian classical
orthography" :-)

But today this one of two branches has two titles--Taraskievica and
classical orthography--which are usually treated equally.
"Taraskievica" means not only the grammar published by Taraskievic
(even his 1918 and 1929 versions are rather diffirent) but this is a
title for the entire branch, so in the respect of the subtag title
everything is ok.

Jaska Zedlik

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Jaska Zedlik | 1 May 11:50
Favicon

Re[4]: be-tarask

G> Hoi,
G> There is the official orthography which is "be". This is also the
G> default for the be code. It is the "be-tarask" that has to identify
G> itself as such.

Gerard, could you please explain why "be" stands only for the official
orthography? According to the ISO 639-1 "be" defines all the
Belarusian language in any form. Nothing is said anywhere about the
defaults for any language including Belarusian. If some particular
variant of the language need to be specified, this need to be done
with the explicit use of a subtag.

Jaska Zedlik
GerardM | 1 May 11:54
Picon

Re: Re[4]: be-tarask

Hoi,
You only need to specify when the content is not what it is to be expected. The official Belarusian orthography is to be expected to be associated with this code otherwise it is insufficient to only ask for one orthography.
Thanks,
    Gerard

On 5/1/07, Jaska Zedlik <sub <at> zedlik.com> wrote:
G> Hoi,
G> There is the official orthography which is "be". This is also the
G> default for the be code. It is the "be-tarask" that has to identify
G> itself as such.

Gerard, could you please explain why "be" stands only for the official
orthography? According to the ISO 639-1 "be" defines all the
Belarusian language in any form. Nothing is said anywhere about the
defaults for any language including Belarusian. If some particular
variant of the language need to be specified, this need to be done
with the explicit use of a subtag.

Jaska Zedlik

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Jaska Zedlik | 1 May 12:21
Favicon

Re[6]: be-tarask

Hi,

sorry, but expected by whom? You may expect the official orthography,
I may expect Taraskievica orthography, nobody knows what may expect
somebody else. What is expected for "de"? Official or "de-1901"?
Therefore to explicitly define the nowadays official German
orthography "de-1996" was registered, because the primary language
subtag "de", as it is said in RFC 4646, is defined by ISO 639-1:2002
and stands for all the German language, without any specific
orthography. 

Is there any document or standard which regulates some particular
orthography for a primary language subtag? Because now I can see only
ISO 639-1:2002 which says that "be" is all the Belarusian language,
not only in the official today orthography.

Jaska Zedlik

G> Hoi,
G> You only need to specify when the content is not what it is to be
G> expected. The official Belarusian orthography is to be expected to
G> be associated with this code otherwise it is insufficient to only ask for one orthography.
G> Thanks,
G>     Gerard

G> On 5/1/07, Jaska Zedlik <sub <at> zedlik.com> wrote:
 G>> Hoi,
G>> There is the official orthography which is "be". This is also the
G>> default for the be code. It is the "be-tarask" that has to identify
G>> itself as such.

G> Gerard, could you please explain why "be" stands only for the official
G> orthography? According to the ISO 639-1 "be" defines all the
G> Belarusian language in any form. Nothing is said anywhere about the
G> defaults for any language including Belarusian. If some particular
G> variant of the language need to be specified, this need to be done 
G> with the explicit use of a subtag.

G> Jaska Zedlik
Yury Tarasievich | 1 May 13:16
Picon

Re: Re[6]: be-tarask

On 01/05/07, Jaska Zedlik <sub <at> zedlik.com> wrote:
> sorry, but expected by whom? You may expect the official orthography,
...

Expected by *everybody*.

Even users of alternative Belarusian know perfectly well *what* stands
for the term Belarusian out of their group. It isn't some vague
"everything" (including slangs, argos, dialects, or micro-languages),
it's the academic codified standard.

In fact, alternative Belarusian users don't often refer to their *own*
language variant without dubbing it "classic".

In short, no subtag is needed yet for the standard Belarusian.

P.S. Kindly restrain yourself from using the abusive term "Narkamauka".

---
Michael Everson | 1 May 13:21
Favicon
Gravatar

Re: Re[6]: be-tarask

Please let's stop talking about Belarusian. The tag has been 
registered. Let's be nice and quiet until there is another tag to be 
discussed.
--

-- 
Michael Everson * http://www.evertype.com
Picon

Re: baku1926


Michael Everson yazmış:
> I have forwarded the subtag modification to IANA, edited suitably
> according to the consensus which it was possible to piece together. Doug
> and I made the final edits; we erred on the side of brevity and
> conciseness while keeping to the spirit of the requests. It was that or
> enter yet another cycle of discussion.
I don't find the Comments entry that was submitted to be well worded. I
can agree w/ the 2nd sentenceö for the most partö for brevıty, but the
first one is doesn't look right.
1) It mentions only 1930s, which could mislead or confuse some people.
2) It has a semicolon after Jeni which breaks a single correct name into
two incorrect names, if i understand ;'s role as a delimiter in this thing.
3) I also suggest changing ';' as a punctuation sign in names list to ','.

I'd appreciate feedback on possibility of changing the Comments from:
Latin orthography used in the Soviet Union in the 1930s
  for writing Turkic languages. Also called New Turkic Alphabet;
  Birl&#x4D9;&#x15F;dirilmi&#x15F; Jeni; T&#xFC;rk
  &#x4D8;lifbas&#x44C;; or Ja&#x14B;alif.

to:
Denotes alphabet used in Turkic republics/regions
of the former USSR in late 1920s, and throughout 1930s, which aspired to
represent equivalent phonemes in a unified fashion. Also known as: New
Turkic Alphabet, Birl&#x4D9;&#x15F;dirilmi&#x15F; Jeni T&#xFC;rk
&#x4D8;lifbas&#x44C;, Ja&#x14B;alif.

4) Lastly, I believe there is no dispute about the following being true
for this subtag, and yet it is not so indicated, as i suggested in
http://www.alvestrand.no/pipermail/ietf-languages/2007-April/006397.html:
Suppress-Script: Latn

I hate to break to you folks, but the tag was jinxed at the last moment:
not the name, hopefully, but the Comments and Suppress-Script for sure.
We measured and measured, and ended up cutting wrong just when we needed
to measure one last time.

I understand the "humanness" involved, but I hope 4 reasons above are
reasons enough to file for corrections. Please let me know if i should
request this in a separate form.

Sincerely,
Reşat.

--
My public GPG key (ID 0x262839AF) is at: http://keyserver.veridis.com:11371
Michael Everson | 2 May 10:46
Favicon
Gravatar

Re: baku1926

At 23:32 -0500 2007-05-01, Reshat Sabiq (Res¸at) wrote:

>Denotes alphabet used in Turkic republics/regions
>of the former USSR in late 1920s, and throughout 1930s, which aspired to
>represent equivalent phonemes in a unified fashion. Also known as: New
>Turkic Alphabet, Birl&#x4D9;&#x15F;dirilmi&#x15F; Jeni T&#xFC;rk
>&#x4D8;lifbas&#x44C;, Ja&#x14B;alif.

I am not really very happy about tinkering so 
soon after registration. But if we do change it I 
would like to get rid of the illegible &xxxx; 
notation. If the registry entries are to be in 
HTML, they should be so normatively, with charset 
tagging so that they display properly. If they 
are not tagged, then ASCII fallback should be 
used so the strings are legible. As it is I can 
only guess, or drag out the Unicode book and look 
them up. That's not legibility.
--

-- 
Michael Everson * http://www.evertype.com
CE Whitehead | 2 May 21:14
Picon

baku1926

Hi, Reshat, all,

I just pasted Reshat's code into a text file, saved it as .html, and opened 
it, pasted it in wordpad, and saved it again as unicode;

I hope the result looks right now in my email, though I am never sure about 
my email;
Reshat can correct it too,
but here is my try, for what it is worth:

"Denotes alphabet used in Turkic republics/regions of the former USSR in 
late 1920s, and throughout 1930s, which aspired to represent equivalent 
phonemes in a unified fashion. Also known as: New Turkic Alphabet, 
Birl&#1241;&#351;dirilmi&#351; Jeni Türk &#1240;lifbas&#1100;, 
Ja&#331;alif."

Take care,
best,

C. E. Whitehead
cewcathar <at> hotmail.com

* * *

Michael Everson everson at evertype.com
Wed May 2 10:46:51 CEST 2007:

At 23:32 -0500 2007-05-01, Reshat Sabiq (Res¸at) wrote:

> > Denotes alphabet used in Turkic republics/regions
> > of the former USSR in late 1920s, and throughout 1930s, which aspired to
> > represent equivalent phonemes in a unified fashion. Also known as: New
> > Turkic Alphabet, Birl&#x4D9;&#x15F;dirilmi&#x15F; Jeni T&#xFC;rk
> > &#x4D8;lifbas&#x44C;, Ja&#x14B;alif.

>I am not really very happy about tinkering so soon after registration. But 
>if we do change it I would like to get rid of the illegible &xxxx; 
>notation. If the registry entries are to be in HTML, they should be so 
>normatively, with charset tagging so that they display properly . . .

_________________________________________________________________
Need a break? Find your escape route with Live Search Maps. 
http://maps.live.com/default.aspx?ss=Restaurants~Hotels~Amusement%20Park&cp=33.832922~-117.915659&style=r&lvl=13&tilt=-90&dir=0&alt=-1000&scene=1118863&encType=1&FORM=MGAC01
CE Whitehead | 2 May 21:27
Picon

be-tarask

Jaska Zedlik
sub <at> zedlik.com
>I don't really think, that they are "VERY different". The difference
>between them are mainly in non-specified then rules and in the
>orthography of foreign words, because it was not relevant in 1929. And
>this difference is certainly less than between 2005 version and the
>official orthography.

Then the way you have the comments is fine!  If there is litte difference 
between the two versions, enough so that no one would prefer to get one 
version or another, no need to distinguish the two.

(There's plenty of the more modern version on the web so obviously the 
subtag is for that primarily.)

Regarding the two forms, the 'classical' and the 'official:'

Whatever Gerard says happens for be without specifying a particular variant 
must be the case at Wikipedia.com;  I do not know what is the case for the 
web in general;
I think it is up to the users of the 'official' version of the orthography 
to decide whether or not they need to register a variant, or leave things as 
they are.

So long as people get served the content they want in the orthography they 
want the way the subtags are , all will be well, and there will be no need 
for any change till things are otherwise in cyberspace.  (Cyberspace has its 
own rules.)

(And, of course, we must wait a bit till the date the browsers and such 
incorporate the new subtags into their functioning before we can see what 
will happen; indeed, I have not been able to get even standard scripts to 
display correctly at the library computer here--even if I tag the language 
and script correctly-- the display here is at the whim of the computer 
settings, has nothing to do with tagging, and the one best way to get 
content in the spellings I want is to type in words in the spellings I want 
and hope they come up.)

Take care,

--C. E. Whitehead
cewcathar <at> hotmail.com

_________________________________________________________________
Don’t quit your job – Take Classes Online and Earn your Degree in 1 year. 
Start Today! 
http://www.classesusa.com/clickcount.cfm?id=866146&goto=http%3A%2F%2Fwww.classesusa.com%2Ffeaturedschools%2Fonlinedegreesmp%2Fform-dyn1.html%3Fsplovr%3D866144

Gmane