In the future sh.wiki hopes to implement an automatic
converter
between Cyrillic, Latin, Ijekavski, and Ekavski, so these
stylistic/dialect/variety issues won't be a problem anymore.
Now, with such conversion, you wouldn't have to worry about edit wars
over what norm is used, because no matter what norm it is written in,
it is displayed in the chosen norm (possibly based on IP range-- users
in Croatia and Bosnia get Ijekavian, users in Serbia get Ekavian;
users in Croatia, Bosnia, and Montenegro get Latin alphabet, users in
Serbia get Cyrillic, but of course you can change these preferences).
Mark
Differences between standard Serbian and Croatian are larger than
just differences of ekavian/ijekavian. A text in Serbian converted
to ijekavian feels to us just a little less Serbian (somewhat Bosnian)
than the original, it's not somehow magically transformed into
Croatian. And please, don't throw NPOV phrases at me, because how
on earth are you going to NPOV-ize loads of technical, scientific
and everyday vocabulary, syntax etc.? Do you plan to write slashes
between variants? Write the same sentence twice? Believe me,
all of this has been tried before, immense force, threats, everything
was applied and the end result was the same – zero.
Elephantus (from Croatian Wikipedia)
--
Odaberite XXLadsl i iskoristite 60 dana neograničenog surfanja za samo 1 kn!
Uz svaki XXLadsl poklanjamo Iskonov glazbeni CD.
http://www.iskon.biz/xxladsl