How to use ways and the files called in the native language?
It is always convenient to call textures, materials and objects in language
which very badly you understand.

Post a reply to this message

LanuHum wrote:

> How to use ways and the files called in the native language?
> It is always convenient to call textures, materials and objects in language
> which very badly you understand.

As with most programming languages, I think this is not possible.
Syntactic identifiers are usually restricted to underscore, digits,
and the letters A-Z or a-z.

For use in text strings (e.g. to render kyrillic text {} object)
you can set the "charset" option to "utf8". You might even use this
to store objects in a "dictionary" based on an array of objects and
an array of (kyrillic) names, but that is not too convenient either.

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:

> As with most programming languages, I think this is not possible.
> Syntactic identifiers are usually restricted to underscore, digits,
> and the letters A-Z or a-z.
>
> For use in text strings (e.g. to render kyrillic text {} object)
> you can set the "charset" option to "utf8". You might even use this
> to store objects in a "dictionary" based on an array of objects and
> an array of (kyrillic) names, but that is not too convenient either.

Now only Povray doesn't support headings in Unicode
Blender is written on С supports
AOI is written on Java supports
Qt on C++  supports
Python supports
Who doesn't support? Borland and Walgrind? Is on whom to equal, aga :)
Very bad!
Now still the shifrator-decoder should be glued in the exporter from Blender in
Povray. :(
Oh!

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> LanuHum wrote:
>
> > How to use ways and the files called in the native language?
> > It is always convenient to call textures, materials and objects in language
> > which very badly you understand.
>
> As with most programming languages, I think this is not possible.
> Syntactic identifiers are usually restricted to underscore, digits,
> and the letters A-Z or a-z.

True enough.  Alas, the computer was not invented in Russia, and Americans got
first dibs on the language of the languages.

> For use in text strings (e.g. to render kyrillic text {} object)
> you can set the "charset" option to "utf8". You might even use this
> to store objects in a "dictionary" based on an array of objects and
> an array of (kyrillic) names, but that is not too convenient either.

LanuHum did not say what operating system he uses, but IIRC, the PovWin IDE does
not support Unicode.  With the Unicode-based editor that I use in Linux, it is
no problem to paste Cyrillic characters into the scene file, and the POV-Ray
back end handles them flawlessly (regardless of the OS), but looking at the file
with the PovWin IDE, the characters look like gibberish.

Post a reply to this message

"Cousin Ricky" <rickysttATyahooDOTcom> wrote:

> LanuHum did not say what operating system he uses, but IIRC, the PovWin IDE does
> not support Unicode.  With the Unicode-based editor that I use in Linux, it is
> no problem to paste Cyrillic characters into the scene file, and the POV-Ray
> back end handles them flawlessly (regardless of the OS), but looking at the file
> with the PovWin IDE, the characters look like gibberish.

My OS - Linux. Fedora-18 and Mageia-3
if cyrillic:
        image_map {

"/home/leonid/Blender/textures/проба.png"
//проба - cyrillic symbol
        filter all 0 transmit all 0}


Konsole wrote:


File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
 Error: Cannot find file '/home/leonid/Blender/textures/          .png',
even after trying to append file type extension.
File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
 Error: Cannot find image file.
Fatal error in parser: Cannot open file.
Render failed

look:spacespacespacespace.png

Post a reply to this message

"LanuHum" <Lan### [at] yandexru> wrote:
> My OS - Linux. Fedora-18 and Mageia-3
> if cyrillic:
>         image_map {
>
> "/home/leonid/Blender/textures/проба.png"
> //проба - cyrillic symbol
>         filter all 0 transmit all 0}

POV-Ray SDL is not HTML.  The correct syntax is
"\u043F\u0440\u043E\u0431\u0430".

> Konsole wrote:
>
>
> File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
>  Error: Cannot find file '/home/leonid/Blender/textures/          .png',
> even after trying to append file type extension.
> File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
>  Error: Cannot find image file.
> Fatal error in parser: Cannot open file.
> Render failed
>
> look:spacespacespacespace.png

I tried an image map both using the correct POV-Ray syntax and copying and
pasting the Cyrillic text directly into the scene file.  As noted, both
techniques work in a text{} object, but it appears that POV-Ray cannot handle
non-ASCII file names or read and write non-ASCII text.  This is a serious
limitation for an international program.

Post a reply to this message

"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> "LanuHum" <Lan### [at] yandexru> wrote:
> > My OS - Linux. Fedora-18 and Mageia-3
> > if cyrillic:
> >         image_map {
> >
> > "/home/leonid/Blender/textures/проба.png"
> > //проба - cyrillic symbol
> >         filter all 0 transmit all 0}
>
> POV-Ray SDL is not HTML.  The correct syntax is
> "\u043F\u0440\u043E\u0431\u0430".
>
> > Konsole wrote:
> >
> >
> > File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
> >  Error: Cannot find file '/home/leonid/Blender/textures/          .png',
> > even after trying to append file type extension.
> > File '/home/leonid/Blender/povray/test/povwip.pov' line 42: Possible Parse
> >  Error: Cannot find image file.
> > Fatal error in parser: Cannot open file.
> > Render failed
> >
> > look:spacespacespacespace.png
>
> I tried an image map both using the correct POV-Ray syntax and copying and
> pasting the Cyrillic text directly into the scene file.  As noted, both
> techniques work in a text{} object, but it appears that POV-Ray cannot handle
> non-ASCII file names or read and write non-ASCII text.  This is a serious
> limitation for an international program.

2.5 years nothing was changed :(
global_settings {
    assumed_gamma 1.000000
    charset utf8
}
#declare Im_Name = concat(chr(1079) chr(1072) chr(1085) chr(1072) chr(1074)
chr(1077) chr(1089) chr(1082) chr(1072) chr(46) chr(112) chr(110) chr(103) )
#declare Material = texture{
    pigment{ image_map{png Im_Name }

==== [Parsing...] ==========================================================
File '/tmp/Empty.pov' line 16: Possible Parse Error: Cannot find file '
 .png', even after trying to append file type extension.
File '/tmp/Empty.pov' line 16: Possible Parse Error: Cannot find image file.
Fatal error in parser: Cannot open file.
Render failed

Post a reply to this message

Am 03.01.2016 um 18:27 schrieb LanuHum:

> 2.5 years nothing was changed :(

This is just to let you know that it's not forgotten; however, any
attempts to add Unicode support for filenames have had me bumping into
brick walls again and again. There's a fundamental structural problem of
the current POV-Ray 3.7 code that needs to be sorted out first, and it
can only be done reliably in many small steps, a tedious process I'm
currently working on once again.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 03.01.2016 um 18:27 schrieb LanuHum:
>
> > 2.5 years nothing was changed :(
>
> This is just to let you know that it's not forgotten; however, any
> attempts to add Unicode support for filenames have had me bumping into
> brick walls again and again. There's a fundamental structural problem of
> the current POV-Ray 3.7 code that needs to be sorted out first, and it
> can only be done reliably in many small steps, a tedious process I'm
> currently working on once again.

Thanks!
Perhaps, it something will help you:
In Linux: that not to rename the file of the image, I create the symbolical
links:
$ ln - s cyrillic_name ascii_name
It works.

Post a reply to this message

"LanuHum" <Lan### [at] yandexru> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 03.01.2016 um 18:27 schrieb LanuHum:
> >
> > > 2.5 years nothing was changed :(
> >
> > This is just to let you know that it's not forgotten; however, any
> > attempts to add Unicode support for filenames have had me bumping into
> > brick walls again and again. There's a fundamental structural problem of
> > the current POV-Ray 3.7 code that needs to be sorted out first, and it
> > can only be done reliably in many small steps, a tedious process I'm
> > currently working on once again.
>
> Thanks!
> Perhaps, it something will help you:
> In Linux: that not to rename the file of the image, I create the symbolical
> links:
> $ ln - s cyrillic_name ascii_name
> It works.

(Linux, btw -- actually Unix in general -- is another obstacle when it comes to
international characters in filenames, at least in theory: There's no way in
heaven or hell to tell Unix to open a file with a given Unicode name, because
Unix doesn't have any notion of character sets at the file system level. To
Unix, a filename is just a sequence of bytes, and it doesn't care whether it is
encoded according to ISO-8859-1, UTF-8, or whatever locale was used when the
file was created. UTF-8 seems pretty common nowadays, but it's not guaranteed.)

Post a reply to this message