 | | | | | |
The LSC has just ratified the LDraw.org Localisation Guideline.
It should be a guideline for implementing localisations for the LDraw System of
Tools.
Read more here: http://www.ldraw.org/Article560.html
Michael Heidemann
On behalf of the LDraw.org Standards Committee (LSC)
| | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Michael Heidemann wrote:
> The LSC has just ratified the LDraw.org Localisation Guideline.
> It should be a guideline for implementing localisations for the LDraw System of
> Tools.
>
> Read more here: http://www.ldraw.org/Article560.html
>
> Michael Heidemann
> On behalf of the LDraw.org Standards Committee (LSC)
Om man skulle tänka sig en svensk version - vilket jag finner tämligen onödigt
med tanke på att vi så gott som tänker på engelska i LEGO-sammanhang - men
alltså om... vad skulle t ex "minifig" bli på svenska? "LEGO-gubbe" har jag hört
nå'n gång. Men "LEGO-gubbe Huvud med Standard Kvinna Mönster" ASG!
Sedan har vi ju regeln om att inte särskriva sammansatta ord, men då blir det
riktigt komplicerat: Det heter väl gubbhuvud, men skulle det inte heta
LEGO-gubbshuvud? Jag kan inte språkregeln som talar om när man ska infoga ett
"s" mellan orden. I den skånska versionen blir det kanske enklare, antar jag:
"gubbahuvud"! :)
För att inte tala om "brick", "plate" och "tile"! Skulle inte tro att de svenska
termerna är särskilt standardiserade, eller...?
När jag och mina bröder var små, kallade vi "studs" för "prickar". Men jag tror
att där finns en standard: "knoppar".
Osv, osv...
/T
| | | | | | | | | | | | | | | | | | | | |
Tore Eriksson wrote:
> In lugnet.cad, Michael Heidemann wrote:
> > The LSC has just ratified the LDraw.org Localisation Guideline.
> > Read more here: http://www.ldraw.org/Article560.html
> Om man skulle tänka sig en svensk version - vilket jag finner
> tämligen onödigt med tanke på att vi så gott som tänker på engelska i
> LEGO-sammanhang - men alltså om... vad skulle t ex "minifig" bli på
> svenska? "LEGO-gubbe" har jag hört nå'n gång. Men "LEGO-gubbe Huvud
> med Standard Kvinna Mönster" ASG!
Jag säger bara en sak: Behåll engelska benämningar!
Om man absolut skall börja översätta så är mina åsikter av typen:
minifig - minifigur (till skillnad mod Technicfigur,
Scalafigur etc.)
studs - knoppar el. pluppar
brick - kloss
plate - platta
tile - slät (platta)
etc.
--
Anders Isaksson
| | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.loc.se, Anders Isaksson wrote:
> Tore Eriksson wrote:
> > In lugnet.cad, Michael Heidemann wrote:
> > > The LSC has just ratified the LDraw.org Localisation Guideline.
> > > Read more here: http://www.ldraw.org/Article560.html
>
> > Om man skulle tänka sig en svensk version - vilket jag finner
> > tämligen onödigt med tanke på att vi så gott som tänker på engelska i
> > LEGO-sammanhang - men alltså om... vad skulle t ex "minifig" bli på
> > svenska? "LEGO-gubbe" har jag hört nå'n gång. Men "LEGO-gubbe Huvud
> > med Standard Kvinna Mönster" ASG!
>
> Jag säger bara en sak: Behåll engelska benämningar!
>
> Om man absolut skall börja översätta så är mina åsikter av typen:
>
> minifig - minifigur (till skillnad mod Technicfigur,
> Scalafigur etc.)
> studs - knoppar el. pluppar
> brick - kloss
> plate - platta
> tile - slät (platta)
> etc.
Oh, PLEASE tell me you're thinking of translating "Minifig" as "Mini-figure".
That would be SUCH an improvement! :-)
-- joshuaD
| | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.loc.se, Anders Isaksson wrote:
> Tore Eriksson wrote:
> > Om man skulle tänka sig en svensk version - vilket jag finner
> > tämligen onödigt med tanke på att vi så gott som tänker på engelska i
> > LEGO-sammanhang - men alltså om... vad skulle t ex "minifig" bli på
> > svenska? "LEGO-gubbe" har jag hört nå'n gång. Men "LEGO-gubbe Huvud
> > med Standard Kvinna Mönster" ASG!
>
> Jag säger bara en sak: Behåll engelska benämningar!
>
> Om man absolut skall börja översätta så är mina åsikter av typen:
>
> minifig - minifigur (till skillnad mod Technicfigur,
> Scalafigur etc.)
> studs - knoppar el. pluppar
> brick - kloss
> plate - platta
> tile - slät (platta)
> etc.
Nä men ge mej en broms. "Pluppar"??? Seriöst, det är ju sån't som ramlar ner i
toaletten när någon gör den stora saken där.
Det finns två minifigurer på Tradera, men hundratals gubbar (t.o.m. en som
föreställer Prinsessan Leia!) och LEGO-figurer.
Klart vi behåller de engelska benämningarna. Jag bara roar mig lite. ;)
/Tore
| | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.loc.se, Tore Eriksson wrote:
> In lugnet.loc.se, Anders Isaksson wrote:
> > Tore Eriksson wrote:
> > > Om man skulle tänka sig en svensk version - vilket jag finner
> > > tämligen onödigt med tanke på att vi så gott som tänker på engelska i
> > > LEGO-sammanhang - men alltså om... vad skulle t ex "minifig" bli på
> > > svenska? "LEGO-gubbe" har jag hört nå'n gång. Men "LEGO-gubbe Huvud
> > > med Standard Kvinna Mönster" ASG!
> >
> > Jag säger bara en sak: Behåll engelska benämningar!
> >
> > Om man absolut skall börja översätta så är mina åsikter av typen:
> >
> > minifig - minifigur (till skillnad mod Technicfigur,
> > Scalafigur etc.)
> > studs - knoppar el. pluppar
> > brick - kloss
> > plate - platta
> > tile - slät (platta)
> > etc.
>
> Nä men ge mej en broms. "Pluppar"??? Seriöst, det är ju sån't som ramlar ner i
> toaletten när någon gör den stora saken där.
>
> Det finns två minifigurer på Tradera, men hundratals gubbar (t.o.m. en som
> föreställer Prinsessan Leia!) och LEGO-figurer.
>
> Klart vi behåller de engelska benämningarna. Jag bara roar mig lite. ;)
>
> /Tore
Your are not forced to use it. But not all people in all countries of the world
are comfortable with english.
Also my son does not speak a good english (at present only I hope) but since I
made translations he is able to find the parts he needs to build.
The translation implementation is not designed for guys like you and me.
It is designed for newbees. In the old DOS/UNIX times you had to know about
english otherwise you could not use a computer. This has changed.
Thats just my thoughts about your valuable posting.
cu
mikeheide
| | | | | | | | | | | | | | | | | | | | | | | |
"Lego-person". Tja, den var faktiskt alldeles ny för mig. :)
http://www.aftonbladet.se/resa/flyg/article6716892.ab
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Michael Heidemann wrote:
> The LSC has just ratified the LDraw.org Localisation Guideline.
> It should be a guideline for implementing localisations for the LDraw System of
> Tools.
>
> Read more here: http://www.ldraw.org/Article560.html
Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
Bricklink) in a foreseeable future?
Philo
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Philippe Hurbain wrote:
> In lugnet.cad, Michael Heidemann wrote:
> > The LSC has just ratified the LDraw.org Localisation Guideline.
> > It should be a guideline for implementing localisations for the LDraw System of
> > Tools.
> >
> > Read more here: http://www.ldraw.org/Article560.html
>
> Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> Bricklink) in a foreseeable future?
>
> Philo
That depends on the authors and the administrators or that items. It is much for
effort to implement this than only to have one language to care about.
Maybe nobody of the above mentioned will ever use that.
I try to implement this in the next versions of my apps where it is useful.
cu
mikeheide
| | | | | | | | | | | | | | | | | | |
In lugnet.cad, Philippe Hurbain wrote:
> In lugnet.cad, Michael Heidemann wrote:
> > The LSC has just ratified the LDraw.org Localisation Guideline.
> > It should be a guideline for implementing localisations for the LDraw System of
> > Tools.
> >
> > Read more here: http://www.ldraw.org/Article560.html
>
> Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> Bricklink) in a foreseeable future?
>
> Philo
Also MLCad can be tuned to use at least the parts description. We have to
substitude the description in the parts.lst with the translation and then you
will see the translation in MLCad.
cu
mikeheide
| | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Michael Heidemann wrote:
> In lugnet.cad, Philippe Hurbain wrote:
> > In lugnet.cad, Michael Heidemann wrote:
> > > The LSC has just ratified the LDraw.org Localisation Guideline.
> > > It should be a guideline for implementing localisations for the LDraw System of
> > > Tools.
> > >
> > > Read more here: http://www.ldraw.org/Article560.html
> >
> > Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> > Bricklink) in a foreseeable future?
> >
> > Philo
>
> Also MLCad can be tuned to use at least the parts description. We have to
> substitude the description in the parts.lst with the translation and then you
> will see the translation in MLCad.
>
> cu
> mikeheide
I have just made my own translation for MLCad of parts.lst. The only problem is
that special characters like the german ä.ö.ü.ß are not shown, as it is read as
pure ascii.
Also the groups in MLCad needs to be tweaked.
If you do a "Scan parts" your parts.lst will be overwritten, so you need to
update that again.
I hope this helps until the specs will be fully implemented in the apps.
cu
mikeheide
| | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Philippe Hurbain wrote:
> In lugnet.cad, Michael Heidemann wrote:
> > The LSC has just ratified the LDraw.org Localisation Guideline.
> > It should be a guideline for implementing localisations for the LDraw System of
> > Tools.
> >
> > Read more here: http://www.ldraw.org/Article560.html
>
> Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> Bricklink) in a foreseeable future?
I will be adding support for this with colors and part names in LDView's "Parts
List" feature. I haven't decided if I should also put it in the Model Tree,
since that's showing actual file data.
--Travis
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Philippe Hurbain wrote:
> In lugnet.cad, Michael Heidemann wrote:
> > The LSC has just ratified the LDraw.org Localisation Guideline.
> > It should be a guideline for implementing localisations for the LDraw System of
> > Tools.
> >
> > Read more here: http://www.ldraw.org/Article560.html
>
> Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> Bricklink) in a foreseeable future?
>
> Philo
That was exactly the question that came up in my community when I started a
discussion about this. 99% of the people who use LDraw use Bricklink. Only a
small percentage of the people who use BL also use LDraw. Consequently it
doesn't seem to make much sense to go through all the work of creating a good
translation and learning to use them if afterwards you need to re-translate
everything back into English to be able to buy the parts you lack on BL.
Don't get me wrong - the translation is not something for me as I'm very happy
using English, but I can see the potential for people who don't and would be
happy to contribute towards this if it was useful for the people in my
community. However, at the moment they are 'forced' to learn the English part
names anyway.
This brings me to another point which is the diverging part naming (and
sometimes also different part numbering) between LDraw and BL. I realise this
may be difficult to overcome, but I see more benefit in standardising that than
in the translation, even if that were to be implemented in BL!
Jetro
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Jetro de Chateau wrote:
> In lugnet.cad, Philippe Hurbain wrote:
> > In lugnet.cad, Michael Heidemann wrote:
> > > The LSC has just ratified the LDraw.org Localisation Guideline.
> > > It should be a guideline for implementing localisations for the LDraw System of
> > > Tools.
> > >
> > > Read more here: http://www.ldraw.org/Article560.html
> >
> > Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> > Bricklink) in a foreseeable future?
> >
> > Philo
>
> That was exactly the question that came up in my community when I started a
> discussion about this. 99% of the people who use LDraw use Bricklink. Only a
> small percentage of the people who use BL also use LDraw. Consequently it
> doesn't seem to make much sense to go through all the work of creating a good
> translation and learning to use them if afterwards you need to re-translate
> everything back into English to be able to buy the parts you lack on BL.
Note that tools like BrickStore allow you to translate LDraw -> BL using part
number mapping.
ROSCO
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Ross Crawford wrote:
> > That was exactly the question that came up in my community when I started a
> > discussion about this. 99% of the people who use LDraw use Bricklink. Only a
> > small percentage of the people who use BL also use LDraw. Consequently it
> > doesn't seem to make much sense to go through all the work of creating a good
> > translation and learning to use them if afterwards you need to re-translate
> > everything back into English to be able to buy the parts you lack on BL.
>
> Note that tools like BrickStore allow you to translate LDraw -> BL using part
> number mapping.
>
> ROSCO
Will Brickstore be made compliant with the LDraw Translation Standard?
What I mean to ask is, will I eventually be able to use the LDraw translation
files to see part descriptions and colours in Brickstore the same way I will in
for example MLCad if I create the translation files?
Jetro
| | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jetro de Chateau wrote:
> Will Brickstore be made compliant with the LDraw Translation Standard?
> What I mean to ask is, will I eventually be able to use the LDraw translation
> files to see part descriptions and colours in Brickstore the same way I will in
> for example MLCad if I create the translation files?
I suggest you contact the BrickStore author and request it.
ROSCO
| | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Ross Crawford wrote:
> In lugnet.cad, Jetro de Chateau wrote:
> > In lugnet.cad, Philippe Hurbain wrote:
> > > In lugnet.cad, Michael Heidemann wrote:
> > > > The LSC has just ratified the LDraw.org Localisation Guideline.
> > > > It should be a guideline for implementing localisations for the LDraw System of
> > > > Tools.
> > > >
> > > > Read more here: http://www.ldraw.org/Article560.html
> > >
> > > Any chance to see this implemented into tools (eg. MLCad...) or website (Peeron,
> > > Bricklink) in a foreseeable future?
> > >
> > > Philo
> >
> > That was exactly the question that came up in my community when I started a
> > discussion about this. 99% of the people who use LDraw use Bricklink. Only a
> > small percentage of the people who use BL also use LDraw. Consequently it
> > doesn't seem to make much sense to go through all the work of creating a good
> > translation and learning to use them if afterwards you need to re-translate
> > everything back into English to be able to buy the parts you lack on BL.
>
> Note that tools like BrickStore allow you to translate LDraw -> BL using part
> number mapping.
>
> ROSCO
How do I do this with Brickstore to show the translated names?? I did not find
any possibility in Brickstore.
cu
mikeheide
| | | | | | |
